
Tuesday May 21, 2013
Simply put, software testing is about making sure that the end product is worth the client’s money and meets the requirements. This usually holds good in a traditional project where the requirements are constant and decided at the beginning of a project. However in an agile environment, where requirements are constantly changing and refactored, testing gets complicated
Traditional Tester |
Agile Tester |
Traditional testers get a specification document detailing the expectation from the product. |
Agile testers use their probing and communication skills to understand the requirements. |
Traditional testers begin testing only after the development cycle is completed. |
Agile testers need to do testing side by side with the development team and give quick feedbacks. |
Traditional testers get adequate time and resources to write detailed test cases/scripts. |
Test cases/scripts take a back seat as testing starts early in the product lifecycle. |
Traditional testers focus on validating and verifying the end product. |
Agile testers also identify faults with design documents, test cases etc. |
Agile testers become better with experience and practice. However, analytical skills and eagerness to learn are two important qualities that all agile testers must possess in order to succeed. Any traditional tester with an attitude to learn, question, suggest and contribute can become a good agile tester.
Download TestingWhiz to implement testing in agile cycles!