Essentials of agile Testing

Essentials of agile Testing

Author: Zhang yuanli

Http://blog.csdn.net/vincetest

Two days ago, the company organized a sharing meeting on the agile development model. For testers, in order to promote the efficient operation of the entire model, the testing was also agile, the following are some key points involved in Agile testing.

I. agility in testing

1. Full participation

Testers participate in the entire R & D process from project initiation to release, rather than submitting the project to the test department for testing after the development is complete. testers must intervene from the demand stage, from understanding the requirements to helping the product personnel to improve the requirements, in many of our projects, testers are often ignored to participate in the evaluation and discussion of the requirements, this is slightly different from the test and Development parallelism mentioned in W model. In the past, V and W models were used, now we are using agile models (where can we share the differences with you ).

2. Starting from the customer

Maintain the overall situation view and stand on the customer's standpoint to ensure that the final release is a good product, not just how many bugs are submitted. This is mainly because the value orientation is different. In a team, no matter what role you are in, the ultimate goal is to make this product a good product, a valuable product that the customer needs, rather than how much each role has paid for this project, the number of bugs submitted, and other performance data.

3. Test drive

Testing drives the entire development process of the product. The tester should not only perform tests, but also do everything that is beneficial to this project, for example, communicate with the customer about requirements clarification, version control, process mechanism, and other transactions.

4. Time agility

Adjust the test strategy based on different iterations (Test Progress, manpower input, and test direction)

5. Not a person

All project personnel participate in the test. Of course, the tester must be the main role. Other developers, product personnel, and other project-related personnel must take some time to test, it is only different from the testing focus and direction of testers. For example, product staff focus more on user experience and benefits. Once problems or problems are found, they are immediately corrected.

 

Ii. Get out of agile misunderstanding

1. Does agile development require documents?

Agility must also require documentation, but it is as detailed as it is not required by the CMMs. We cannot rely solely on documents to help us improve our efficiency, but some framework-based documents must be necessary, especially basic requirements. This will help project members understand the general intent of the entire project. In the agile process, we must manage document changes (because changes are everywhere ).

Many people think that Agility focuses on communication, which is totally correct. But we cannot replace documents with verbal or basic emails because of this lack of document support. This is just a mess, too agile!

2. Does the agile development mode conflict with project management?

There is no conflict at all, but there are some differences in values. In fact, in a sense, if the project management is not well done, it will directly enter the agile mode, which is a great leap and difficult to implement, for example, the change management and communication management involved in project management are all required by agile models and some basic work methods. Therefore, project management is a foundation.

3. Is agility a good medicine for good changes?

Obviously, agility is not a good medicine for changes. the R & D process of a product will certainly involve many changes, but our direction cannot be changed. For example, we need to make a flower roll at the beginning and finally change it to a steamed stuffed bun, in fact, such changes cannot be tolerated. It is feasible to change the color shape of the volumes.

The changes involved in agility refer to the iterative process that allows customers to quickly confirm feedback and ultimately form a very clear requirement, rather than making changes at will, in the case of unclear requirements, the technical staff are not exhausted yet.

Iii. agile requirements

1. Overall product planning and requirements (including future product trends)

If we compare a product to a child, the product manager is like the parent of the child. As a parent, we must make some plans for the child's growth, in this way, it is conducive to the growth of the child and the continuous correction of the growth route according to the child's feedback during the growth process. In this way, the parent is a qualified parent.

2. iterative planning requires product staff to develop and focus on controlling

Similar to the previous one, it only shows that product personnel are the key to product success or failure and the soul of the product. product managers have a great responsibility.

3. The Division of iterations should follow the testability principle (ensure that each iteration is a test that can execute a complete operation flow)

In an iteration plan, testers need to consider whether the testability of each iteration is optimal. It cannot be a semi-finished product that cannot be tested and evaluated after iterative development, there is no value to show, and there is no evaluation feedback. If we cannot provide valuable things for the next iteration, we should not iterate and directly merge them with others.

4. demand changes during iteration must be implemented on text or charts.

5. Change the original W test mode to iterative test.

6. The document process is only an auxiliary tool, mainly relying on timely and effective communication (how to weigh between documents and communication is a matter of degree and never go to the extreme ).

Welcome to repost this article, reprinted please indicate the source of the article: Zhang yuanli's blog http://blog.csdn.net/vincetest