Agile testing theory and practice-5

[This is the fifth article in Agile testing theory and practice (article 1, article 2, article 3, article 4, article 5, article 6, article 7 )]

 

 

In the previous article "using tools to achieve agile development", I have already talked about the current development situation of our company and I will not repeat it here. It is mainly about using devsuite of techexcel.
System to manage the entire process. As for many people, I may ask why tools are needed for agile development or testing. For simple projects, the efficiency of using tools is reduced, because just a few lines of code and a few functions can be completed at once. It is a waste of time to get a tool.

 

However, for a slightly larger project, you may not be able to manage the project well without tools. For example, a team has implemented 10 functions in an iteration cycle, the tester found 40 bugs a day, but the repairer (because some people are still working on the function) can only repair 20 bugs at most every day. What about the remaining 20 bugs, of course, it is delayed until the next day is repaired. An iteration cycle is usually one to two weeks. If two weeks are better, if 20 bugs are needed every day, I have accumulated 200 bugs that have not been fixed. If there are no defect management tools, I may only use Excel documents to manage these bugs. For a single user, Excel has actually done a good job of saving information, the report is also very good, but think about so many development and testing needs to open the same Excel file, view, update, I believe that Excel data will be messed up, and Excel cannot be tracked, there is no way to set the process. For example, if I want to know how many states this bug has experienced and how many people have handled it, I cannot find it.

 

So is the tool useful? I think it is still useful. For large and medium-sized projects, since I want to use agility, I suggest using tools. Otherwise, this agility will definitely become less agile at last. Just like taking a bus, if the road is 100 meters, I suggest you still walk (Agility) Forget it, because the bus is still starting, parking, and other traffic lights, maybe you are walking faster than it; if it is a 10 km road, of course you will choose the bus (Tools). For agility, because it is composed of many iteration cycles, each iteration cycle is equivalent to a 100 m, but the combination of many iteration cycles has become 10 km. True agility is just a guiding ideology and does not specify how you must do it (there are various implementation methods). Therefore, in normal work, we need to match your agile model based on the actual situation of each company.

 

As long as you search for "agile testing" on Baidu, I believe you can find a lot of content, which has a summary and details. Take a closer look, you will find that many people think that agility is definitely like this, and that is not the case. Of course, the descriptions of "this" are not very similar. There are only two reasons for analysis, one is purely self-blind, and may be a little bit tricky, but it is not actually used, just according to your own ideas, Chaos analysis; the other is actually in use, therefore, Let's explain agile in the context of our company. Of course, I am talking about agility based on my company's situation, so I will not demand your use of my theory, I just hope you can find some useful knowledge from my articles, so I am very happy.

 

Well, let's talk less about it. No matter whether you understand why you need the tool, I will continue (if you have any questions, you can talk about it privately ).

 

Devsuite of techexcel has been introduced before and has been used all the time. It feels quite helpful, but I will not introduce it here, let's give a picture and explain the products we will use. Otherwise, if we mention a product, we may not know what it is.

 

 

For agile testing, the following three products are required:

1.Devspec: Requirement management, used to design the inspection function of testers (design testers)

2.Devtrack: Defect tracking management. It is used by testers to test and submit bugs based on functional design documents and track the bug progress.

3.Devtest: Test management tools, used to manage test cases, and use test cases to generate test plans and perform tests (including automated tests)

These three products can be integrated or used separately. Of course, they are integrated for use.

 

Next I will introduce the implementation of agile testing in our company according to the actual test process.

 

1. Demand design stage:

Our company is also developing products, mainly for developing CRM products, like other software companies, to release each of our versions, we first need to collect customer requirements to develop corresponding features, develop new features by ourselves, and view and Research features that surpass competitors.

 

This part of work is mainly carried out in devspec. devspec is mainly used to manage requirements and assign requirements for development to start, and it will be applied to each function (regardless of the customer's or their own, or research from competitors) to create a new entry. Each entry has its own attributes, including the title, owner, and status. You can customize any attributes you want to add. Then, the owner can log on to the system to view the entries allocated to him. After processing, the owner must change the status to the next state and assign it to the appropriate owner. For testing, we set a status called"Test Review"Status. Generally, when a requirement reaches this status, our design and testing personnel will handle this requirement. The way to handle it is generally starting with the original document, check whether the current design conforms to the original document. If there is any discrepancy, he will talk to the designer and then repeat the entry"Need to be redesigned"Status. After the designer completes the operation, the status will be changed again. After the tester passes the review, the"To be developed"Status.

 

It is emphasized that at this stage, the so-called design tester may not have to be a full-time engineer. He may be a project manager or someone else, however, he must be a person with the ability to judge whether the design idea meets the requirements and has the right to let the designer design again.

 

This is what testers need to do in the requirement design stage. The following is a devspec image as the end of today's article (to be continued)