Video: Traits in SpecFlow

Sophie Keiblinger from TechTalk has taken time out from her testing duties to share a couple of insights into how she and her team use traits (tags) in SpecFlow. This ranges from keeping track of the user stories associated with changes to scenarios, using traits to communicate the status of tests with other team members and managing which tests should be executed for different builds.

2 replies
  1. A Concerned Citizen
    A Concerned Citizen says:

    There are some serious issues in the approaches used in this video.

    For starters, why add version control information in text in your scenarios? You’re just cluttering up the place with junk – will your users want to read that stuff? Linking scenarios with user stories is not necessary. When a story is done, it’s done, you no longer care how you got there. Move on. If you think you need that information, most likely there are issues with your process.

    Also, having a tester write scenarios and throw them over a wall to a developer is just as bad as having a developer write code and throw it over a wall to a tester. The point of doing tests first is that it is part of the design process. The fact that you have tests is a (really great) bonus. Writing tests first is not the point of TDD.


Trackbacks & Pingbacks

  1. […] Anatomy of a Gherkin (From Dan) “I found a good article about Gherkin which we are currently using for our UI Test automation. TSG also uses Specflow for unit testing in Master Crew project. This is a good article for anyone who is unfamiliar with gherkin/cucumber/specflow, or just wants to brush up. I also found a useful video related to specflow.” […]

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *