Create 009-break-data-driven-test-into-multiple-tests-objects.md #52
Conversation
|
|
|
I have one other use case for the same need. The use case is behavior-driven development using TickSpec (https://github.com/fsprojects/TickSpec). TickSpec is a .NET framework for BDD tests that allows generating tests from feature files on runtime instead of compilation time. The benefit of runtime generation is that business people can write new tests just with feature file changes when they reuse existing steps. When you use BDD then you have many feature files which each contain several scenarios. We are able to generate on runtime when using NUnit or xUnit tests that show in Test Explorer as a test per scenario. When we try the same with MSTest we only get one test in Test Explorer. It is unusable even with just 20 scenarios and you can have many more, thousands. |
| 1. DataTestMethod Attribute should allow the option to treat it's tests as separate test objects. | ||
| 2. Should not alter current behavior for existing users. | ||
|
|
||
| ### Proposed solution |
There was a problem hiding this comment.
There are multiple ways to data drive a test.
- using DataRow
- using DynamicData
- directly extending ITestDataSource
Is your proposal for all of these approaches?
|
Closing this as we are moving repository to the main one. Also, I opened a ticket for us to revisit documentation of existing behaviors. |
5 participants
RFC 009 for Issue 450.