Behavior Driven Development has been around for a while, and it is here to stay. However, the added abstraction levels present in it, pose a technical problem for writing and managing tests. While it does a great job of marrying the non-technical aspect of test writing, to the technical flow of an application under test, keeping this information under source control becomes problematic. Frameworks such as Behave, Cucumber or Robot give subject matter experts that additional ability to write test cases, however, they are often restricted to access to them, as if test cases are treated as code, they stored in source control repositories. Additionally, frequency these Given, When, then steps soon grow to an extent where they become difficult to manage without an IDE, and most non-technical people don’t want to run an IDE.
Through the use of Management Tools such as JIRA, and VersionOne, Max will show how to simply manage these non-technical steps and keep them in sync with the automaton in an SCM, such as Git or SVN. Additionally, he’ll discuss and show how to link these tests to requirements, and stories in development, to provide traceability, and continuous integration support. He’ll share his hands-on experience developing an open sourced product to help manage these tests, along with proven workflows at an enterprise level for ensuring full team buy-in on both non-technical and technical aspects of test case development.