Skip to content

feat(scanner): detect .NET web and test tooling#26

Open
Will-thom wants to merge 1 commit into
EShener:mainfrom
Will-thom:will/agent-ready-dotnet-web-tests
Open

feat(scanner): detect .NET web and test tooling#26
Will-thom wants to merge 1 commit into
EShener:mainfrom
Will-thom:will/agent-ready-dotnet-web-tests

Conversation

@Will-thom

Copy link
Copy Markdown

Fixes #22.\n\nAdds scanner coverage for ASP.NET Core and common .NET test tooling. The scanner now reads relevant .csproj and Program.cs files, reports ASP.NET Core when web app signals are present, and surfaces xUnit, NUnit, MSTest, and Microsoft.NET.Test.Sdk package references as framework/tooling context.\n\nValidation:\n- npm test\n- node --check src/scanner.mjs\n- node --check test/scanner.test.mjs\n- git diff --check\n- node bin/agent-ready.mjs doctor\n\nNote: npm run check could not be executed through npm in this local Windows environment because npm/Node attempted to access a denied path at C:\Users\itdev\Desktop before running the script. The touched JavaScript files were checked directly with node --check.

@Will-thom

Copy link
Copy Markdown
Author

I checked this against the current main before attempting the conflict resolution. The .NET web/test detection from this PR appears to have been superseded by main already: main includes .NET project signals, ASP.NET Core detection, .NET Test SDK/xUnit framework detection, dotnet restore/build/test commands, fixture coverage, and docs updates.

Because rebasing this branch would duplicate the current implementation, I left the branch untouched. Happy to close this if you agree it is now covered by main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add ASP.NET Core and .NET test framework detectors

1 participant