As enterprises attach importance to software quality, software test engineers are more and more popular, and their requirements for job seekers are also increasing. They not only require job seekers to have solid theoretical foundation, but also have rich practical experience, which increases the difficulty for software test engineers to find a job. Today qian Feng teacher to share some common software test interview questions and answers.

1. What is the software lifecycle and its model?

A: Software life cycle is also called Software life cycle. It refers to the whole process from the beginning of the development of software concept to the end of the use of the software. Generally speaking, the entire life cycle includes planning (definition), development, operation (maintenance) three periods, each period is divided into several phases, each phase has a clear task.

2. The role of software configuration management? What does the software configuration include?

A: Software Configuration Management (SCM) is a technique for identifying, organizing, and controlling changes. Software configuration management is applied to the entire software engineering process. Change is inevitable as software is built, and change adds to the confusion among software developers on a project. The goal of an SCM activity is to identify changes, control changes, ensure that changes are implemented correctly, and report changes to other interested parties. In one sense, SCM is a technique for identifying, organizing, and controlling changes in order to minimize errors and maximize productivity. Software configuration includes configuration item identification, workspace management, version control, change control, status report, and configuration audit.

3. What is a basic testing process for your company?

A: Will first needs analysis meeting, participants have products, development and testing, mainly investigate the features of demand point, after finished, development regarding the schedule of development, we can according to the competent written plan, assigned to the task of writing test cases, case review will be carried out in after you’ve written to have changes to review the modified version form the final cases, After the developer version is compiled, we will execute the test according to the test cases. During the test, we will submit the bug, track the bug, and write the test report after the test.

4. What are test cases? What methods are used to write test cases?

A: A test case is a specific set of input data, operations, or various environmental Settings, and expected results provided to the system being tested for the purpose of conducting the test. A test script is a script written for automated testing. The test script must correspond to the corresponding test case.

There are two methods of test cases, white box test: logical coverage, circular coverage, basic path coverage; Black box test: boundary value analysis, equivalence class division, error guess method, causality diagram, state diagram, test outline method, random test, scene method.

5. How to submit high quality software Bug records?

Answer: 1) Universal UI should be unified and accurate. The UI of defect report should be consistent with the UI of the tested software for easy locating.

2) Try to use terminology and expression methods commonly used in the industry to ensure accurate expression and professional expression.

3) Each defect report shall contain only one defect.

4) Non-reproducible defects should also be reported.

5) Clearly indicate the type of defects, summarize and judge the type of defects according to the phenomenon of defects.

6) Clearly indicate the severity level and priority level of defects.

7) Description, concise, accurate and complete, reveals the essence of defects and records the location of defects or defects.

8) Use automatic numeric numbering between short lines and use the same font, size and line spacing.

9) Try to record only one operation per step.

10) Make sure the steps are complete, accurate and brief.

11) According to the defect, can choose whether to carry on the image capture.

12) Check for spelling and grammar defects.

13) Try to use phrases and short sentences and avoid complex sentence patterns.

14) Description of defects.

6. Brief the tracking process of the BUG management tool

Take BugZilla for example

The tester finds a BUG and submits it to Bugzilla with the status new. The recipient of the BUG is the developer interface. The development interface assigns the BUG to the developer of the relevant module, changes the status to assigned, and the developer and test confirm the BUG. If it is my BUG, set it to receive. If the problem is caused by another developer, it is forwarded to the next developer. If it’s not a problem, it needs to be discussed and confirmed, rejected, and then the tester closes the problem.

If the developer accepts the BUG and fixes it, change the BUG status to fixed and tell the test in which version it can be tested. The tester tests in the new version and rejects validation if the problem persists. If it has been fixed, close the BUG.

During the interview, you can tell whether a person is confident and dare to take responsibility from the way he answers questions. Of course, good preparation is the foundation of victory, and only by knowing yourself and knowing your enemy can you win a hundred battles. If you want to learn more about software testing skills and interview skills, you can come to Qianfeng Education for an audition.