Tests as Documentation (IPC14)

October 28, 2014 15:53

With automatic software tests, we ensure that our application (or certain parts of it) behaves like intended. Even if new requirements are added, our tests tell us if our old requirements are still fulfilled. A well maintained set of tests may also serve as a catalog of requirements, but usually only the developers are able to read those tests. BDD tools like Behat might change this. Let's have a look at how human-readable tests could be used as a communication tool for developers and stakeholders.



Alexander M. Turek


more decks of the speaker