Testing was no longer a role that a developer (often reluctantly) had to do it. Testing was a field, with separate training and certification programs. Testing this also was much more structured. It was thought in advance about the tests to be carried out. There is a risk analysis was carried out, and test techniques have been applied, whereby a certain depth could be guaranteed. Therefore, more errors were found during the testing phase and could also be given better judge the quality of products
.
Agile in pure form
the major drawback of this method is that test hand was relatively expensive and lead times of realization processes were often longer. That was because a separate test phase was inserted after the software was realized.
And with the rise of Agile testing is also the subject up for discussion again. If agile is applied in the most purist shape, there are only developers. These developers are responsible for everything that has to do with the realization of the software, including testing. I have experienced a number of projects in recent years where this pure form of Agile was used. You noticed it was generally find that software was previously delivered as positive, but the downside was that there was relatively less errors were found by the developers than testers. And thus there were also more production incidents.
Team Roles and human behavior
That’s easily explained. Testing is something that people think is in the blood or not. A tester is someone who is inquisitive and like to try things this is constantly learning from mistakes, structured proceed, positive critical and attention to detail. Such a person will have in your team needs.
The British researcher Belbin defined nine team roles based on human behavior. A team performs according to Belbin best if most of these roles are represented. The testers I know are in Belbin terms generally Care Carriers (the perfectionist finishers) and / or monitors (thoughtful analyzer). Developers generally possess more characteristics of the plant (creative soloist) and / or the Source Researcher (ideas connector). The beauty is that these roles are complementary according to Belbin. Both types of individuals are required in order to achieve success. In a team with only developers according to this theory coined the best ideas and realized. Only exists the danger that these ideas do not correspond to the needs of the customer and the products also do not meet the desired quality. The testers are required in order to ensure that the fulfillment of the needs of the customer. They are therefore often called the “quality conscience of a team.
broaden Horizon
I believe in the basic principles of Agile. So test the project as early as possible. And as a tester you have to have development skills so that you can work well with developers and can play an important role in setting up unit and technical testing. On the other hand, developers should develop test skills in order to assist in minimizing the performance of tests and thus the critical path (test phase).
Testing will always therefore in my view be a separate box testers, where specific behavioral skills are required. Well I think the testers have to broaden their horizons. On the one hand they need to expand their technical skills so they can support developers in their work. Think specify and automate unit testing. This may also be started earlier system and acceptance tests. On the other hand I think the focus should always come to lie on preventing errors (first time right). The tester will herein within the team play an important role. Based on experience and previously detected errors he will facilitate the team in continuously improving processes
.
No comments:
Post a Comment