You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Outside units, could we have something based on user supplied use cases that has offline test data paired with the today's examples .yml's
This could mean pairing those .yml examples with proper offline test data and maintaining repositories for data driven testing to ensure functionality on use-cases wise persists between releases outside the unit testing world and the tool continues to work for people who submit use-cases that in turn pushes to ensure wide range of working use-cases would be covered?
e.g. I would like to feed in examples with "offline test data" that could be tested automatically in isolation easily thats not always covered by units but more like full "use-case didn't break test"
I did see there are plenty of units great job!
Outside units, could we have something based on user supplied use cases that has offline test data paired with the today's examples .yml's
This could mean pairing those .yml examples with proper offline test data and maintaining repositories for data driven testing to ensure functionality on use-cases wise persists between releases outside the unit testing world and the tool continues to work for people who submit use-cases that in turn pushes to ensure wide range of working use-cases would be covered?
e.g. I would like to feed in examples with "offline test data" that could be tested automatically in isolation easily thats not always covered by units but more like full "use-case didn't break test"
To illustrate:
https://twitter.com/thepracticaldev/status/733908215021199360
The text was updated successfully, but these errors were encountered: