What does iterative testing mean?

Question 1: In software testing, what is the difference between versions and iterations? I'm begging for expert guidance. In fact, I don't think there is any difference. It's just that the terms are different. They are both large-scale projects. They are divided into different modules and completed step by step in different periods. Each iteration is a cycle. Just take what you want to do. A large website takes a year to complete, but the first version only requires login and registration, and then testing. This version is completed and we will continue with the next iteration. I hope it can help you

Question 2: Recruitment" In the information "Software Test Engineer", what is unclear about what it means to participate in planned version and iterative version testing?

"Participate in testing" is understandable, don't say you don't know what software testing is... that's dead...

"Participate in version testing" is understandable, right? Unit testing, not integration testing, is version testing.

"Participate in planned version and iterative version testing", which means participating in the testing of 2 versions.

If you don’t understand anything above, just ask, I’m going to write a book for you.

The only thing that may be unclear in this sentence is what is a planned version and what is an iterative version.

These two concepts are in agile development (they are also used in other development models, and the concepts are the same).

Let’s talk about the planned version first, which is generally considered to be a big one. Stage, the final software version of the period. Mostly in units of one and a half years, but also in units of several years.

The iterative version is a small stage. Since agile development requires that at each minimum stage, the incorporated code must ensure that the currently compiled version is available. Therefore, this usability must be tested, which is the iterative version. Generally, a week (or 2 weeks), or a month or so, is an iterative version, and this development process of small stages is called an iterative process.

It is also a version test. What is the difference between testing the planned version and the iterative version? Because the iterative version is released very quickly, it is impossible to fully test all the content in one iteration, so iterative version testing is useful. Critically, iterations focus on modifications and newly developed content, and secondary on content that has not changed.

Planned version testing is a comprehensive, fine-grained integrity test.

Question 3: How to test and write test cases if you encounter version iteration? 1 Prepare a key business test case. (Main business scenario) Each version iteration needs to be tested

2 Correspond to the modified use cases for the added functions, and conduct tests corresponding to the modifications. It should be noted that the modification points affect the functions involved.

Question 4: Performance testing is required for each version of iteration Is it? Iterative testing and performance testing are not concepts at the same level. Whether to conduct performance testing should be determined according to the needs of the product, not whether it is iterative testing

Question 5: When software testing encounters version iteration, what should you do? How to deal with it If the version iteration is relatively fast, automated testing will be considered.

Question 6: During iteration, is there a difference between regression testing for small requirements and large requirements? No difference~~~~~~~~

Question 7: Software testing encounters iteration How to deal with debugging?

Set loop variables

Step by step~

Question 8: Product development iteration speed is accelerating, how to test to keep up? superior? As a veteran engineer of TestBird, I understand what you mean. After the product is released, new features will be continuously added. In addition to new features before each release, the old core features must also be ensured before release.

However, the use cases of new functions are directly added to the archive and the priority will not be modified. The priorities of some paths in the new functions of the current version are level 1 and level 2, but when viewed from the perspective of the entire version Maybe it's not that important.

Modification or deletion of old functions, modification or abandonment of existing functions, use cases are also directly archived, and no previous use cases are modified or deleted, although there are written at the end of the use cases that need to be modified at the end version, but because the number is too large, it is difficult to find the point to modify.

You need to streamline the use cases. The method is as follows: experience accumulation + code coverage + knowledge base

1. Make full use of experience and transform it into visible things. That is to use collective wisdom

The first round: manual screening, because we need to be good at using the experience of outsourced classmates

Strength: rough, not too detailed, and boldly delete each module

2. Tool assistance: code coverage knowledge base

Use tool assistance to supplement manual deficiencies and redundancies

Improve the knowledge base of the entire module to facilitate Follow-up utilization

In addition, I also recommend functional automated testing, you can try it.

Question 9: After the iterative version comes out, should the product manager first confirm whether the requirements are realized before handing it over to the test? This depends on the company regulations, but I personally think that after the iterative version comes out, the product manager should first confirm whether the requirements are realized and then Deliver it to testing, because this is equivalent to testing the product iteration twice, and reduces the trouble caused by unclear requirements~