Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • Boromir agrees. Commented Mar 20, 2015 at 16:27
  • Sounds like you know your process and you don't get stuck between concept and unit test. Would you mind sketching the flow in terms of tools / artifacts (in the .Net stack if possible). (e.g., "I use accept stories in Accept3000, which automatically create system tests in SuperSystemTesterNet, then for each one I ..., which integrates into NUnit tests") Commented Mar 20, 2015 at 16:35
  • @toddmo I think you are getting into area of "opinion" and "which tool to use" which are both off-topic here. In this case, it is heavily on what fits you and your project. I believe this is not possible without some level of experimentation. Some people are simply able to model the whole thing in their head while others need some kind of tool to help visualize the whole design flow. Commented Mar 20, 2015 at 17:13
  • are you a .net developer? if i post a question on "software recommendations" will you answer it over there? I'm stuck without ~a way of doing it~. Thanks. Commented Mar 20, 2015 at 19:38