The Testing Strategy and Types of Tests
•
0 gostou•466 visualizações
The document discusses different types of software tests, including unit tests, functional tests, load tests, soak tests, end-to-end tests, integration tests, and exploratory tests. It also covers how developers, QA teams, and customers are involved in testing as part of the development process. The document uses an example of implementing a feature to allow commenting on tasks to illustrate how to develop a test plan and consider the tradeoffs between testing different quality attributes. It emphasizes that testing should be integrated into the development process and that QA teams are part of the overall development team.
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (6)
Destaque
Semelhante a The Testing Strategy and Types of Tests
Semelhante a The Testing Strategy and Types of Tests (20)
Mais de Agile Toulouse
Mais de Agile Toulouse (20)
The Testing Strategy and Types of Tests
- 1. The Testing Strategy Domenico Musto 2012 October
- 3. Who am I? 25/10/12 www.agiletour.com
- 4. About me 25/10/12 www.agiletour.com
- 5. Not about me 25/10/12 www.agiletour.com
- 6. What do I do? C# .NET Team leading Web REST Ruby Automation Testing Agile @mimmozzo domenico.musto@gmail.com 25/10/12 www.agiletour.com
- 7. Today we talk about.. • Differences between types of tests • Tests and developers • Tests and QA 25/10/12 www.agiletour.com
- 8. ..we don't talk about.. • Testing frameworks • Libraries 25/10/12 www.agiletour.com
- 9. The Agile Testing Quadrant 25/10/12 www.agiletour.com
- 10. Technology facing 25/10/12 www.agiletour.com
- 11. Types of tests • Unit • Functional • Load • Soak 25/10/12 www.agiletour.com
- 12. Unit tests • They test units of code in isolation • Interaction between components • Describe the behaviour • Drive the design • Fast execution 25/10/12 www.agiletour.com
- 13. Be careful • Test just public interfaces • Do not abuse of mocking 25/10/12 www.agiletour.com
- 14. Adding a new class is not the trigger for a new test. The trigger is the implementation of a new requirement. 25/10/12 www.agiletour.com
- 15. Functional tests • They test the interaction with components outside the context of our application • They assure integration • They might be slow 25/10/12 www.agiletour.com
- 16. public class When_getting_an_object_from_the_db { static int _objectId; static DbWrapper _sut; static object _object; Establish that_there_is_an_object = ()=> { _objectId = 100; ManuallyAddAnObjectInTheDb(_objectId); } Because we_get_the_object = ()=> _object = _sut.Get(_objectId); It should_get_the_object = ()=> _object.ShouldNotBeNull(); } 25/10/12 www.agiletour.com
- 17. public class When_storing_an_object_in_the_db { static int _objectId; static DbWrapper _sut; static object _object; Establish we_have_an_object_to_save = ()=> { _objectId = 100; } Because we_save_the_object = ()=> _object = _sut.Save(_objectId); It should_store_the_object = ()=> _sut.Get(_objectId).ShouldNotBeNull(); } 25/10/12 www.agiletour.com
- 18. Be careful • Do not mix tests • Use context builders for data fixture 25/10/12 www.agiletour.com
- 19. Load tests • Feedback on performance • Feedback on volume limit • Complicated to write • Slow execution 25/10/12 www.agiletour.com
- 20. Soak tests • Discover technologic issues • Slow execution 25/10/12 www.agiletour.com
- 21. Business facing 25/10/12 www.agiletour.com
- 22. Types of tests • End to end • Integration • Exploratory 25/10/12 www.agiletour.com
- 23. End to end tests • They test the whole scope of a feature • They are acceptance tests • Understandable from non-techincal persons • Slow execution 25/10/12 www.agiletour.com
- 24. They are not (only) interface tests. 25/10/12 www.agiletour.com
- 25. Integration tests when the end to end aren't brave enough • They test pieces of the application • They test the integration • Slow execution 25/10/12 www.agiletour.com
- 26. Exploratory tests • Manual • Look for feature limit 25/10/12 www.agiletour.com
- 27. Let's implement a feature 25/10/12 www.agiletour.com
- 28. The actors of the development process • Developers • QA • Customer 25/10/12 www.agiletour.com
- 29. The story As a user of huddle I would like to add comments to tasks to collaborate better with my colleagues 25/10/12 www.agiletour.com
- 30. 25/10/12 www.agiletour.com
- 31. 25/10/12 www.agiletour.com
- 32. 25/10/12 www.agiletour.com
- 33. 25/10/12 www.agiletour.com
- 34. 25/10/12 www.agiletour.com
- 37. df 25/10/12 www.agiletour.com
- 38. The feature is ready 25/10/12 www.agiletour.com
- 39. 25/10/12 www.agiletour.com
- 40. What about the tests ?!?!?! 25/10/12 www.agiletour.com
- 41. 25/10/12 www.agiletour.com
- 42. When do I need to do end to end tests ? 25/10/12 www.agiletour.com
- 43. Test plan 25/10/12 www.agiletour.com
- 44. 25/10/12 www.agiletour.com
- 45. 25/10/12 www.agiletour.com
- 46. Test plan • Acceptance tests • Functional tests • Integration tests • Unit tests 25/10/12 www.agiletour.com
- 47. 25/10/12 www.agiletour.com
- 48. Trade-off 25/10/12 www.agiletour.com
- 49. Quality attributes • Availability • Modifiability • Performance • Security • Testability • Usability 25/10/12 www.agiletour.com
- 50. The test pyramid 25/10/12 www.agiletour.com
- 51. QA Team 25/10/12 www.agiletour.com
- 52. QA Team 25/10/12 www.agiletour.com
- 53. QAs are part of the dev team 25/10/12 www.agiletour.com
- 54. The reputation of the tests, of the build server and of the development environment 25/10/12 www.agiletour.com
- 55. The deployment 25/10/12 www.agiletour.com
- 56. 25/10/12 www.agiletour.com
- 57. Thanks. Q&A @mimmozzo domenico.musto@gmail.com 25/10/12 www.agiletour.com