Swtbok Practice Test Series (2)--you will submit the test developer version number back?

Developers struggle very much late and submit the final version of the test.

They can be mitigated. But the bad news came quickly that the software did not pass the predictive testing team (in order to ensure that the developer submits the basic functionality of the code validation or business process in the test process). Development manager Wang. Quickly find the manager who is responsible for the predictive test.

Wang said , "Lao Zhang, what's going on?" What's the problem? We are not easy to develop, how can you not test the version number back?

Lao Zhang said: you have submitted the version number is too poor quality. Without our pre-test, we need to change again. To meet our requirements. We have the ability to test. You look at the two problems we found.

Lao Wang did not look at these two problems, but directly questioned Lao Zhang: I heard that your recent test environment to build a problem. Do you want to borrow the version number to call back time to toss your test environment AH? Not for our development to give you cover Ah!

Test teams are often plagued by the low quality of the submitted version number. Once the development team submits the version number quality is too low. A number of serious problems can be found during the testing process, resulting in large numbers of test cases being blocked. And it's unfortunate that. In case of a bad change in project publication time. This will lead to the Test team can actually run the test time is compressed, resulting in a test task can not be timely completion of the quality. Calling back the version number also disrupted the development team's progress at the same time as it affected the Test team.

So some teams used a pre-test (sometimes called a Smoke test) method. The Test team will conduct a formal test run only with the version number of the pre-test.

The above scenario is a conflict caused by a pre-test failure when a pre-test is carried out.

The test personnel are not only the goalkeeper, but also should take the initiative when needed. Although setting up a pre-test is a way to improve the quality of the version number received by the test, the use of a pre-test is not intended to call the version number back. After all, go back. I'm going to come back again.

The testers were passively waiting for the development team to submit the version number. Should actively help the developers, as far as possible, they can be tested by the pre-test.

In some projects. The Test team is proactive in helping developers conduct code reviews before testing runs. It will also help the developers to do part of the test work, thus avoiding the passive waiting. The development team interacts well with the Test team to get the project done together. After the initial quality improvement, the developer can also have a small amount of development manpower to help the Test team during the test personnel running test.

The entry criteria should also consider the factors that test themselves at the same time considering the development factors. It is usually the test staff to check the developer's work, but the test staff's own work is often not adequately supervised and checked. In addition to the requirements for the quality of the previous phase of the developer's activities, the entry criteria are set. The test team should be prepared for the conditions also to be bound. For example: test environment in place. Assessment of the trial example. Self-initiated test script writing, test data preparation, and so on.

An objective entry criterion with operational and monitoring access.

Although the entrance guidelines are for testing activities, they should not be conducted solely by the Test team, but should be discussed in a broader context. Can include developers and project managers. At the same time, activities that occur in compliance with the test export guidelines are not necessarily run by test teams. For example: The test can be completed by the development team itself, and the Test team examines the test results. But suppose that the pre-test tests the example itself, but the blur. The same tests that run on different people may have different test results, which can cause unnecessary trouble.

Copyright notice: This article Bo Master original articles, blogs, without consent may not be reproduced.

Swtbok Practice Test Series (2)--you will submit the test developer version number back?