The approach and strategy used in Agile testing methodologies is normally very different from the usual bureaucratic methods. In fact the variation could be due to different project teams and project needs. In many cases, it is more sensible to not have a separate team for testing. This statement should not be misunderstood. By not forming a separate team, we don’t mean the process of testing is any less vital. The fact is the testing can be carried out in shorter times, by the professionals who are accustomed to the objectives of the systems and its functionality very well.
Business Analysts can Work as Testers:
For example few teams can have their business analysts carry out testing every time a new version of the software is rolled out. This is so because they totally understand the requirements of these software and they precisely test them to check if they work as per the needs. The developers may also test these software packages. They understand the system much better than anyone else and cross check the results in a more subtle manner. Agile software development demands unorthodox and innovative thinking and people from different backgrounds with right mind set should be picked for performing the testing.
What is to be tested?
As the turn around time in these methodologies is short, it becomes important the team that is working on the testing is crystal clear about the things that should be tested. Though innovation and close interaction between the team members are promoted more than the usual processes, strong emphasis is given on the efforts that need to go into testing. Every team on the job may have different context based group dynamics, but every single code should go through unit testing. The developers carry out unit testing to make sure software unit functions correctly.
As the process of development is iterative in nature it is quite possible that the code releasing next was built after modifying the earlier one. Hence, the process of regression testing becomes significantly important in these kinds of situations. The team finally test if the added functionalities in the code work fines and if the functionalities that released earlier still work as before.
Different Steps of Effective Testing in Agile Methodology:
The one and only way to have an effective testing strategy at place is by making sure enough testing effort, either manual or automated, and enough testing coverage. The biggest challenge often come in the form of less documentation, but the biggest advantage should be made out of closer communication amongst team members, which should naturally result in great understanding of the system and clearer thought process.
Importance of Regression Testing:
Every time there is a change in code, regression testing should be done. Combination of different people who execute Test Cases and automated scripts assure test coverage. Exploratory Testing should also be promoted. These aren’t pre-defined or pre-designed; the Tests get executed and designed in no time. Ad hoc testing can also be encouraged. These kinds of testing are carried out by skilful and experienced testers.
Bugs found during Agile Testing:
It is possible that a small code gets a bug as and when a code is enhanced, changed or modified by any developer. It is also possible that a working code, which was working earlier is now broken. Newer bugs or defects may get introduced at every step when a piece of code undergoes a change. While there are Test Cases that assure timely execution, it might not be possible for all kinds of teams to script and design different test cases.
Criss Derek works as a senior manager at an IT firm that follows the Agile software testing methodology and recommends everyone to follow the Agile approach to improve productivity in their organization.
Himadri is a part time blogger. He loves to write on technology and technology related tips & tricks. Blogging is his passion! He is an Electronics and Telecommunication Engineer.