Build Test---BVT of software testing

1. Basic process of construction:

A. Developers writing source code files on their personal computers
B. They store the prepared files in a single centralized place, and the build group compiles all the source code into binaries that can be run on the computer, and uses the installation tool to package the various files that need to be installed on the server into packages that can be installed on different platforms.
C. Combine into a product

The process of building is like assembling a production line, the source code file is a variety of size accessories, is stored in a large warehouse, source code, some in the construction process also need to be processed.

2. Build process:

3. When building a production line, the software Development department, especially the build Test team, needs to consider what.

A. "Warehouse" where the source code is stored
B. "Pipeline" that can be produced repeatedly
C. Fast and simple testing to ensure that products can be tested more thoroughly and in-depth using system backup technology to share test environments

4. Source code is the basis of the construction process, how to put the source code in a safe and reliable place.

In general, the source code will be stored in the database, using the version control system to manage the source code.

5. Version control System Overview

It is used to help us document the process and details of file changes, typically based on the client/server architecture, which can serve multiple developers at the same time.

6. What are the features of the version control system?

Create new files, extract files, save new versions of files, coordinate or control multi-person changes to the same file, record the history of file changes, and make inquiries.

7. What are the prerequisites for building a product?

Build a built environment.

8. What factors to consider when building a built environment.

A. Choosing a server to build using
B. Select the Build Environment platform
C. Build the software or tools you need

9. Software development process:

A. Developers write software code to give source code to build groups to build
B. Build group make the source code file into a software product that can be installed, and then give it to the Test team for testing
C. Test group feedback to the development team on the issues found during testing
D. The development group modifies the code and then gives the modified code to the build group to build the new version

10. In the design of the construction process, generally also take into account the overall construction and the need for partial construction, the key to design part of the construction logic.

The relationship between each source code file and the build step time, the General version control system supports the change of source code file during the query phase, which guarantees the feasibility of the partial construction.

11. The automation section builds the process:

12. What are the benefits of the partial build portfolio?

A. If the source code has not changed since the last build, the build can be skipped to shorten the overall build time
B. If there are no sequential relationships between parts of the build, they can be run simultaneously to shorten the build time
C. The binary code generated by the partial build can be applied directly to the test environment to quickly test the new product functionality, and if passed, some of the build code goes to the next version of the test product

13. How to avoid the build process as a bottleneck for development.

Shorten build times and reduce problems in the build process, such as automating builds.

14. Benefits of automated builds.

A. Ensure that the software development process can be customized to a more flexible construction schedule
B. Ensuring consistency of each build process without introducing product defects due to perceived errors

15. General principles of the automated build process:

A. When the source code file changes, there is no need to build program changes, even if there are unavoidable changes, it should make the process of change as easy and simple
B. Avoid writing the output or input parameters directly to the build code, so that the built environment changes without changing the build program
C. Some variables that often need to be changed are unified management of attribute files and need to be changed only by modifying the parameter values in the properties file (such as the *.properties file, or the *.xml file)
D. Using template files and XSLT to build the build Program files based on build requirements at build time to reduce input to change build program Files

16. How often the software is built is determined.

Determined according to the needs of the software test. In an Agile development model environment, it is critical to provide frequent test products. The most likely guarantee of the build frequency is a necessary guarantee in the software Agile development model.

17. What is build testing. --build Verification Test

Build testing is also known as building an acceptability test (build acceptance test), typically after each test product is built, the build Test team executes a set of the most basic test cases to determine whether the quality of the test product being made can be delivered to each test group for a more comprehensive, More in-depth requirements for each test.

Building testing is mainly from the functional point of view to build test products to verify that the construction of the test is successful implementation of other tests to start the prerequisite, efficient building testing can improve the overall team testing efficiency.

18. How the test cases for building tests are selected.

Test cases for building tests are basically functional test cases, relatively short, and should focus on the most basic and important functions of the product, the selection principle:

A. Test only the most important and basic functions
B. Test only the use cases that have been tested and are relatively stable

19. What is the role of building tests?

A. Let the developer know immediately whether the new version of the source code can be successfully constructed into a software PRODUCT
B. Helping test teams avoid wasting time on test products that are unstable or not working at all

20. Steps to build the test:

A. Install the test product and other required software
B. The system configuration required for the product
C. Test some of the most basic product features

21. Build the content of the test.

The construction test is also a test of the construction process itself, the main content includes:

A. Confirm that the build includes a new change to the source code file
B. Check the built logs for errors
C. Whether the final product file size is abnormal, etc.

22. Build the test diagram:

23. Steps when building a test environment.

A. Use a number of tools to automate the system configuration, as part of the build test, and automatically install all the software that is needed to build the test.
B. Use some system backup and recovery tools:
I. Back up the installed system to build the software required for testing
Ii. backing up the build environment itself

24. What is the purpose of building the test?

Verify that the product build process has been successfully completed and that the product is measurable.

25. What is static testing?

Static testing analyzes the source files directly, discovers problems, and is suitable for situations where problems can be found in the source files.

26. What are the common static test cases?

Grammar and spelling test, web affinity test, Java/java EE best practices or user-friendly rule checking

27. Automatic static test diagram: