Hot answers tagged agile-testing
The best reference to design your test cases is API documentation a.k.a API contract. This document describes: How to call the APIs What to expect from them Generally, you can have these kind of test levels for your APIs (based on the contract): Acceptance testing Contract testing e.g. pack (includes your idea: schema validation) Performance testing
Do not clean data Usually it adds more problems than it solves: If you clean data in tests, the tests may fail (e.g. process is killed) and thus the DB won't be clean. If you clean data with external scripts - you'd have to write and maintain them separately. Even more - you'd have to not forget to run them from your local machine. This doesn't solve ...
Let me answer your queries in a different way i.e. not by looking at the number of testers and developers and how to utilise them during the initial phases of development cycle. TDD and TFD tries to emphasise on a very important aspect of SDLC which in the long term helps in reducing testing costs and helps to launch a product on time if not sooner. ...
Only top voted, non community-wiki answers of a minimum length are eligible