Skip to content
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

Jump to bottom

NUnit3: Make FixedNameTestMethodBuilder the default strategy #862

Closed
zvirja opened this issue Oct 6, 2017 · 1 comment
Closed

NUnit3: Make FixedNameTestMethodBuilder the default strategy #862

zvirja opened this issue Oct 6, 2017 · 1 comment
Assignees
@zvirja
Labels
enhancement
Milestone
4.0 rc1

Comments

@zvirja
Copy link
Member

zvirja commented Oct 6, 2017

Currently we have the known issue about manual actions for full NUnit integration support with VS and NCrunch runners. We should make the FixedNameTestMethodBuilder strategy the default one in v4, so everything works out-of-the-box.

If later user find that it needs volatile names for better diagnostic, they could change the default strategy in the way described in the known issue.
@zvirja zvirja added this to the 4.0 milestone Oct 6, 2017
@zvirja zvirja changed the title NUnit3: Make FixedNameTestMethodBuilder the default one NUnit3: Make FixedNameTestMethodBuilder the default strategy Oct 6, 2017
@zvirja zvirja mentioned this issue Oct 6, 2017
Merged
@zvirja zvirja self-assigned this Oct 6, 2017
@zvirja
Copy link
Member Author

zvirja commented Oct 13, 2017

Done! Strategy will be default in v4.

@zvirja zvirja closed this as completed Oct 13, 2017
@zvirja zvirja mentioned this issue Oct 17, 2017
Closed
28 tasks
@zvirja zvirja mentioned this issue Jun 7, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zvirja zvirja

Labels
enhancement
Projects
None yet
Milestone
4.0 rc1
Development

No branches or pull requests
1 participant
@zvirja