As enterprises to pay attention to software quality, software test engineer acclaimed, the requirements for job seekers is also increasing, not only require job applicants to have a solid theoretical foundation, but also a wealth of practical experience, which gives software test engineer job more difficult. Work today Feng gave you share some common software testing interview questions and answers.
1, and what the software life cycle model?
A: The software life cycle (Software life cycle), also known as software life cycle, survival. It refers to the formation of the development software from concept, later developed software, known to lose the whole process until the demise of use value. In general, the whole life cycle including planning (define), development, operation (maintenance) three periods, each in turn divided into several stages, each stage has a clear mandate.
2, the role of software configuration management? What software configurations include?
A: Software Configuration Management (Software Configuration Management, SCM) is a logo, revise, organize and control technology. Software Configuration Management applied to the entire software engineering process. Change is inevitable when the software is established, it changed exacerbated the confusion between the software developer projects. Target SCM activities is to identify changes, control changes to make sure the change is implemented correctly and other relevant personnel reporting changes. In some ways, SCM is a logo, and tissue modification control technologies aim is to minimize any error and the most effective to improve production efficiency. Software configuration includes the following: Configuration item identification, workspace management, version control, change control, status reporting, configuration auditing.
3, what a basic test procedure is to test your company?
A: First will be held needs analysis meeting, participants have a product, development and testing, is to discuss some of the major features point demand, after the expiry of the development to develop on schedule, we are the competent written plan, assigned to write test cases task, will be finished after the use-case review, the assessment has to modify the modified finishing the final version of the use case, after the development of the staff compiled version, we will come to perform testing in accordance with test cases, test process, submitting bug, tracking bug, until the close, after testing, preparation of test reports.
4. What test? What method will be used when writing a test case?
A: The test is a test for the implementation of the input data provided to the system under test, various environmental or operating settings and a particular set of desired results. Test scripts are scripts for automated testing and write, write test scripts must correspond to the corresponding test cases.
There are two test methods, white box: logical coverage, covering cycle, the basic path covered; black box testing: boundary value analysis, equivalence partitioning, the error guessing method, a causal diagram, a state diagram, a test outline France, random testing, scenario method.
5, how to submit high-quality software defects (Bug) record?
A: 1) General UI to be unified and accurate. UI UI bug reports to be consistent with test software, easy to find positioning.
2) make use of expression the terms and expressions conventional industry, to ensure accurate expression, reflects the specialization.
3) Each defect report includes only one defect.
4) non-reproducible defect must report.
5) clearly indicate the type of defect according to the defect phenomenon, summed to determine the type of defect.
6) clearly indicate a serious defect levels and priority levels.
7) Description (Description), concise, accurate, complete, revealed defects in real terms, recording the location of a defect or defects.
8) Use short line between automatic digital number, using the same font, font size, line spacing.
9) Each possible to record only one operation step.
10) validation step complete, accurate, and brief.
11) The defect, choose whether to perform image capturing.
12) Check spelling and grammar defects.
13) Try to use phrases and short sentences, avoiding complex sentence sentence.
14) defects description.
6, briefly BUG tracking process management tools
Using as an example BugZilla
Testers found BUG, submitted to Bugzilla, the new new state, BUG recipient who is a development interface; BUG development interface assigned to the relevant developer module, modify the assigned status, developer and confirmation testing BUG. If my BUG, is set to receive; if another developer is a problem, then forwards it to carry out this behavior by the next developer; If you think that is not a problem, then we need to discuss and confirm, reject the BUG then the tester to close this issue.
If the developer accepted the BUG, and after a good modify, amend the BUG status as fixed, and inform the test version in which you can test. Testers to test the new version, if you find the problem persists, then the authentication is denied; if you have to repair, turn off the BUG.
In the course of the interview, answering questions from the way, we can see that this person is confident, whether courage to take responsibility.