Skip to content

fix mstest sdk eval timeout #558

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Evangelink merged 5 commits into from
Apr 21, 2026
Merged

fix mstest sdk eval timeout #558

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
e4480c9
Fix timeout in MSTest.Sdk v3-to-v4 eval scenario 9
Evangelink Apr 17, 2026
c793459
Fix CI timeout in migrate-mstest-v3-to-v4 eval scenario
Evangelink Apr 20, 2026
33f2daf
Strengthen net6.0 scenario prompt for reliable skill activation
Evangelink Apr 20, 2026
e333516
Merge branch 'main' into dev/amauryleve/fix-mstest-sdk-eval-timeout
Evangelink Apr 20, 2026
7f57593
Merge branch 'main' into dev/amauryleve/fix-mstest-sdk-eval-timeout
Evangelink Apr 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Fix timeout in MSTest.Sdk v3-to-v4 eval scenario 9 
The fixture csproj had MSTest.Sdk/3.8.0 while the prompt claimed the user
already upgraded to 4.1.0. This mismatch caused the model to edit the
csproj and run dotnet build, triggering slow MSTest SDK NuGet downloads
that exceeded the 240s timeout on CI.

- Update fixture csproj to MSTest.Sdk/4.1.0 to match the prompt
- Add specific CS error codes to the prompt so the model provides direct
  fixes instead of building
- Update rubric item to reflect the project already being on 4.1.0
  • Loading branch information
@Evangelink
Evangelink committed Apr 17, 2026
commit e4480c9e176047e47a51adf8ca9d609414c71107
12 changes: 8 additions & 4 deletions tests/dotnet-test/migrate-mstest-v3-to-v4/eval.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -371,9 +371,13 @@ scenarios:

- name: "Migrate MSTest.Sdk v3 project using ManagedType and TestTimeout"
prompt: |
I have a test project using MSTest.Sdk/3.8.0. The tests use TestContext.ManagedType,
TestTimeout.Infinite, and TestContext.Properties.Contains. After upgrading to
MSTest.Sdk/4.1.0, I get compilation errors. How do I fix them?
I upgraded my test project from MSTest.Sdk/3.8.0 to MSTest.Sdk/4.1.0 and now I get
these compilation errors:
- CS1061: 'TestContext' does not contain a definition for 'ManagedType'
- CS0103: The name 'TestTimeout' does not exist in the current context
- CS1061: 'IDictionary<string, object>' does not contain a definition for 'Contains'
How do I fix these errors? Also, is there anything else I should know about
MSTest.Sdk v4 behavior changes?
setup:
files:
- path: "TestProject.csproj"
Expand All @@ -391,7 +395,7 @@ scenarios:
- "Identifies that TestContext.ManagedType is removed in v4 and recommends FullyQualifiedTestClassName"
- "Identifies that TestTimeout.Infinite is removed and recommends int.MaxValue"
- "Identifies that TestContext.Properties.Contains must become ContainsKey"
- "Notes the MSTest.Sdk version should be updated to 4.1.0"
- "Notes the project is using MSTest.Sdk/4.1.0 or confirms the SDK version upgrade"
- "Mentions that MSTest.Sdk v4 no longer adds Microsoft.NET.Test.Sdk when using MTP"
timeout: 240

Expand Down
2 changes: 1 addition & 1 deletion tests/dotnet-test/migrate-mstest-v3-to-v4/fixtures/v3-sdk-project/TestProject.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
<Project Sdk="MSTest.Sdk/3.8.0">
<Project Sdk="MSTest.Sdk/4.1.0">

<PropertyGroup>
<TargetFramework>net8.0</TargetFramework>
Expand Down