Hot answers tagged

2

BDD Tests As many things around us - there is more hype around BDD than what it deserves. BDD was born as a way of naming your tests clearer: instead of saying that you test this-and-that you're saying it-should-work-this-and-that. And this is a great idea since it makes it clear about the purpose of the test and it allows the test to be shared with not-so-...


2

You probably have read that BDD is not about testing, but about improving communication. In software development, there are a manifold of ways to express the same thing; and some fit better for each role. Given that, it is common for a project to have many documents expressing the same thing. This cause two problems: When requirements change, all these ...


1

Prior to automating a test case/test pack the checkpoints must be agreed. If you are purely automating a functional test case which does not validate how long it takes between one step and the next, in that case as long as the agreed journey is automated and functional checkpoints are met, the test case/pack is considered to be completed from scripting ...


1

Automated testing is done when all the current functionality is covered by the tests, i.e. test case coverage. When the automated testing is done I always recommend manual testing on top of this. If you have specific performance and/or load tests they will have criteria as to whether they are passing or failing, i.e. completing within the time specified.



Only top voted, non community-wiki answers of a minimum length are eligible