Technovation By SKS

I am expressing my views and learning on Agility for Testing. This article highlights the challenges and solution when one has to do the testing alongwith the development. What approach for testing should be taken when “Time to market” is an important factor. The solution of course is to utilize testing time alongwith the development. But is it such an easy task for tester or developer or for management? Of course, not. To successfully overcome such a situation requires commitment and support from the entire project stakeholder but more support, coordination and commitment are required among test team and development team. The process that should be followed to overcome such a situation is mentioned below: 1. Define your Test Strategy 2. Define your team and assign responsibility 3. Do not wait for a formal process of release 4. Keep doing the testing as soon as build is ready for testing (Do not wait for formal release) 5. Always keep in mind that tester and developer are wor...

From programmers to users, everyone involved in software development agrees: Testing is good. So why so many systems are so badly tested? There are several problems with the traditional approach to testing: · If testing is not comprehensive enough, errors can make it into production and cause potentially devastating problems. · Testing is often done after all the code is written, or at least after the programmer who wrote the code has moved on to other things. When you are no longer living and breathing a particular program, it takes some time and effort to back into the code enough to deal with the problems. · Often tests are written by programmers other than those who wrote the code. Since they may not understand all of the details of the code, it is possible that they may miss important tests. · If the test writers base their tests on documentation or other artifacts other than the code, any extent to which those artifacts are out of date will cause problems. · If tests are n...