This website uses cookies. By continuing to browse the site, you are agreeing to our use of cookies
Testing
November 25, 2016
The software industry has evolved into various new development models such as Agile and DevOps, cutting across the product to market and application support landscapes. The traditional ways of testing have also gone through significant changes and are evolving constantly.
We are aware of the regular responsibilities of a tester in a scrum/agile development model; similar to V-Model, the tester’s contributions start right from the design stage i.e. story grooming stage. The tester is involved in all the development-related communication threads, including bug fixes from unit testing. This ensures the key focus areas to test when the code moves to the QA stage. The tester is responsible for the collection and publishing of all the key project metrics such as ‘story turnover rate to QA’ and ‘story points for bug fixes’.
Below facets would add value to any testing engagement in the long run, enhancing the value-add a tester contributes to the industry. An application/product with 3+ years of development road map ahead, along with the existing production support need, would be an ideal candidate:
The focus on ‘effort maximization’ with ‘automation’ and ‘shrink IT cost’ has never been more imperative; an ‘undying will to learn new skills’ and ‘an eagerness to go the extra mile’ are the key to unleash the new age testers.
Every outcome starts with a conversation