Entry-level----test execution, Environment building, daily build, test logging and tracking, regression testing, test summary and reporting

The test case is prepared for the purpose of performing the test.

Setting up the test environment

　　(1) test data: Some tests require the use of large quantities of data, such as capacity testing, stress testing, etc. Depending on the specific testing requirements of the product, it may be necessary to insert large amounts of data into the database tables, prepare a large number of files, generate a large number of socket packages, etc.

(2) Some tests require specialized external hardware devices, such as printers, barcode readers, card readers, fingerprint testers, etc.

If it's a mobile app test, you might want to have all of your supported models ready. Some of these devices can be simulated using simulators, while others cannot. Simulator such as the Night God Android Simulator. Often encountered in the mobile phone simulator can execute the program, run on the real phone will be a problem, or in the PC Report table format is correct, but the real print out will be shifted, aliasing.

(3) Some products need to support a variety of operating systems, then before doing the compatibility test need to prepare a variety of operating system computers, or you can consider the virtual machine to install, such as VM ware,virtual pc.

(4) Some tests need to be deployed to multiple machines, and various parameters need to be set up, so you need to have a variety of installation packages ready before testing.

(5) Some tests need to use the network, settings need to consider the network routing settings, topology, etc., then before testing the need to prepare such network equipment and network environment configuration.

BVT Test and smoke test

　　BVT Testing (build verification test), compile the check test, mainly check whether the source code can be correctly compiled into a new, fully available version. If the BVT does not pass, the tester cannot get the new version to test.

Smoke test, the concept comes from the field of hardware production, generally by the manufacture of the circuit board power, see whether the power of the board, if the design is unreasonable, it may be in the power of the same time immediately smoke, the circuit board is not available, so there is no need for the next step of detection.

Then the concept applies to software testing, in fact the meaning is consistent. is mainly to verify the main function, if the main function is not feasible, then there is no need to verify, directly back to the developer to modify the build.

It is important to note that the test cases for smoke testing should evolve with the depth of development.

The basic process of building daily

　　The integration of the program module is a common cause of development progress. Defects are also often concentrated in the integration phase, especially if the interface design is not good enough software.

The final solution to the integration problem is early integration, continuous integration, and small version integration. Build on a daily basis to achieve continuous integration, iteration integration, and version integration verification.

Daily builds are the process of compiling, connecting, and composing an executable program on a daily schedule.

The daily build is usually built at night and is automatically built with free time, so it's also called nightly. A simple process such as

Standardize code management with daily builds

　　Daily builds, in addition to resolving some version integration issues, can also be prescriptive about the programmer's source code check-in behavior.

As we all know, if the programmer does not follow a certain specification check-in, check out the source code, it is likely to lead to other programmers code module failure or confusion. A correct and prudent approach should be to get all the new versions and compile all the code before checking in the code you've modified, and make sure that you don't check in when someone else's code is not affected, or you have to solve the problem first.

　　The daily build is a morale-boosting mechanism, and everyone in the project team is able to see what new features are added to the new build, see the products that work, and make it a little bit more everyday than the day before and enhance it like seeing your child grow up, giving everyone a sense of confidence and encouragement.

Entry-level----test execution, Environment building, daily build, test logging and tracking, regression testing, test summary and reporting