1. What is included in a software defect (or Bug) record? How to submit high-quality software defect (Bug) records?
A bug record should basically include: number, module to which the bug belongs, bug description, bug level, discovery date, discoverer, modification date, modification person, modification method, regression result, etc.; to effectively find a bug, refer to requirements and detailed Design and other preliminary documents design efficient test cases, and then strictly implement the test cases, fully confirm and affirm the problems found, and then release them to the outside to improve the quality of bug submissions.
2. What are the required fields for bugs?
A bug message needs at least the following items: bug number, bug severity level and priority, bug-generated module, etc.
First, there must be a bug summary, explaining the general content of the bug; second, find out the version corresponding to the bug, a detailed description of the bug, including some screenshots, videos, etc.; finally, the test environment when the bug occurs, and the conditions that are generated are the corresponding operation steps .
3. Briefly describe the life cycle of BUG?
Submit -> Confirm -> Assign -> Fix -> Verify -> Close
4. How should software defect levels be divided?
Category A: Serious errors, including the following errors
1) Illegal exit due to crash caused by the program;
2) Infinite loop;
3) A deadlock occurs in the database;
4) Program interruption caused by wrong operation;
5) Function error;
6) Connection error with the database;
7) Data communication error;
Category B: more serious errors
1) program error;
2) Program interface error;
3) Constraints such as completeness are not added to database tables, business rules, and default values;
Category C: General errors
(The operation interface is wrong, including whether the definition and meaning of the column names in the data window are consistent)
2) The printed content and format are wrong;
3) Simple input restrictions are not placed in the foreground for control;
4) No prompt is given for the delete operation;
5) There are too many empty fields in the database table;
Category D: minor errors
1) The interface is not standardized;
2) The description of the auxiliary instructions is unclear;
3) The input and output are not standardized;
4) The user is not prompted for long operations;
5) The prompt window text does not use industry terminology;
6) There is no obvious distinguishing mark between the input area and the read-only area;
Test process and method
1. What do you think is the key to doing a good job in test cases?
Understanding of requirements and design documents, familiarity with the system.
2. What do you think is the key to doing a good job in test cases?
1) Find bugs;
2) Avoid defects in the software development process;
3) measure the quality of software;
4) Pay attention to the needs of users;
The overall goal is: to ensure the quality of the software.
3. What stages should a complete set of tests consist of?
Test planning, test design and development, test implementation, test review and test conclusion.
4. What does the software acceptance test include?
Formal acceptance testing, alpha testing, beta testing.
5. What are the strategies for system testing?
Function test, performance test, reliability test, load test, usability test, strength test, security test, configuration test, installation test, uninstall test, file test, fault recovery test, interface test, capacity test, compatibility test , distribution testing, usability testing.
6. Describe the life cycle of software testing activities?
The test cycle is divided into planning, design, implementation, execution, and summary. in:
1) Planning is to plan all activities in the entire test cycle, estimate workload and risks, arrange human and material resources, arrange progress, etc.;
2) Design is to complete the test plan and plan the test from the technical level;
3) Implementation is to design test cases and test procedures;
4) Execution is to execute test cases according to the plans, schemes, use cases, procedures and other documents completed in the previous period.
Summary: Record the test results, conduct test analysis, and complete the test report.
7. Briefly describe the "80-20 principle" in software testing. (Just understand it)
(1) 80% of software defects often exist in 20% of the software space;
(2) 80% of software defects can be found and avoided in the testing work, and subsequent acceptance tests can help us find 80% of the remaining defects. Range, will be exposed after long-term use;
(3) 80% of software defects can be found by means of manual testing, and 20% of software defects can be found by means of automated testing. Because there is an overlap between the two, there are still about 5% of software defects that need to be discovered and corrected by other means.
8. Describe in detail the complete process of a test activity.
1) The project manager completes the requirements document through communication with the customer, and the developers and testers jointly complete the review of the requirements document. The content of the review includes: where the requirements description is unclear and where there may be obvious conflicts or functions that cannot be realized . The project manager completes the project plan by integrating the opinions of developers, testers and customers. Then SQA enters the project and starts doing statistics and tracking
2) The developer completes the requirement analysis document according to the requirement document, and the tester conducts a review. The main content of the review includes whether there are any omissions or differences in understanding between the two parties. The tester completes the test plan document, and the content included in the test plan is described above;
3) Testers start to write test cases according to the modified requirements analysis document, while developers complete the outline design document and detailed design document. These two documents become supplementary materials for testers to write test cases;
4) After the test case is completed, the test and development need to be reviewed;
5) Testers build the environment;
6) The developer submits the first version, there may be unfinished functions that need to be explained. Testers conduct tests and submit to BugZilla after finding BUG;
7) Development and submission of the second version, including bug fixes and some added functions, for testers to test;
8) Repeat the above work, generally after 3-4 versions, the number of BUGs will decrease and meet the requirements for shipment;
9) If there is a problem with customer feedback, testers are required to assist in reproduction and regression testing.
9. According to your own understanding, answer what is software testing and what are the stages of software testing.
Software testing is the process of running software in order to find bugs in it, and a successful test is one that finds hitherto undiscovered bugs. Software testing is generally divided into unit testing, integration testing and system testing.
10. What stages should a complete set of tests consist of? Explain each stage separately.
Planning phase, design phase, white box unit, white box integration, black box unit, black box integration, system testing, regression testing, acceptance testing. A complete set of tests should consist of five phases:
1) Test plan First, define the corresponding test demand report according to the specifications of the functional requirements and performance indicators in the user demand report, that is, formulate the highest standard for black box testing. All the testing work in the future will be carried out around the testing requirements. The application program that meets the testing requirements is qualified, otherwise it is unqualified. At the same time, it is necessary to properly select the test content, and reasonably arrange the test personnel, test time and test time. resources etc.
2) Test design decomposes and refines the test requirements formulated in the test planning stage into several executable test processes, and selects appropriate test cases for each test process (the quality of the test case selection will directly affect the effectiveness of the test results. sex). A common software testing interview question A common software testing interview question.
3) Test development establishes a reusable automatic test process.
4) Test execution Execute the automatic test process established in the test development stage, and track and manage the found defects. Test execution generally consists of steps such as unit test, combination test, integration test, system joint debugging and regression test. Testers should In a scientific and responsible manner, the test is carried out step by step.
5) Test evaluation combined with quantified test coverage and defect tracking reports to comprehensively evaluate the quality of the application software and the work progress and work efficiency of the development team.
11. What do you think is the key to doing a good job in test case design?
The key to white-box test case design is to cover as many internal program logic results as possible with fewer test cases;
The key to black-box use case design is also to cover module output and input interfaces with fewer use cases. It is impossible to test thoroughly to find the most problems in a reasonable amount of time with the fewest use cases.
12. Black-box testing and white-box testing are two basic methods of software testing. Please explain their respective advantages and disadvantages!
Advantages of black box testing:
1) Relatively simple, no need to understand the code and implementation inside the program;
2) has nothing to do with the internal implementation of the software;
3) From the user's point of view, it is easy to know which functions the user will use and what problems they will encounter;
4) Based on the software development document, it is also possible to know which functions in the document are implemented by the software;
5) It is more convenient when doing software automation testing.
Disadvantages of black box testing:
1) It is impossible to cover all the code, and the coverage rate is low, which can only reach 30% of the total code amount;
2) The reusability of automated testing is low.
Advantages of white box testing:
Help software testers increase code coverage, improve code quality, and discover hidden problems in code.
Disadvantages of white box testing:
1) There will be many different paths for the program to run, and it is impossible to test all the running paths;
2) The test is based on the code, which can only test whether the developer is doing right, but cannot know whether the design is correct or not, and some functional requirements may be missed;
3) When the system is huge, the test overhead will be very large.
13. What is the difference between Beta testing and Alpha testing?
Beta testing (β testing), testing is a test performed by multiple users of the software in the actual use environment of one or more users. Developers are usually not on the test site. Alphatesting (α testing) is a test conducted by a user in a development environment, or a controlled test conducted by users within the company in a simulated actual operating environment.
14. The composition of a defect test report.
(1) The name of the test software project. Each software project to be tested has a unique name, and some companies have a specific number for the project.
(2) Test the software version number. During the test period, it is generally necessary to test multiple software versions. When reporting an error, you must correctly fill in the software version number that caused the error.
(3) The name of the tester, which is easy to distinguish responsibilities and easy to manage.
(4) The test date and time are convenient for analyzing and counting error report information.
(5) Test the software environment, including the operating system and other necessary software programs.
(6) Test hardware environment, including configuration information of test computers and other test equipment.
(7) Error description, which briefly describes the characteristics of the error, which is convenient for query and quick browsing.
Errors include the following:
a) Error identification number (ID#), each error has a unique identification number for easy query.
b) Error type, according to the type of error, assign appropriate personnel to handle the error.
c) Error level, the severity of the error and the priority of processing. Priority is given to high-level errors.
d) Error status. The error status indicates whether the error has been processed and how to handle it. According to the error status, an appropriate processing method is adopted.
e) The name of the error handler, which is convenient for distinguishing responsibilities and easy for management.
f) The operation steps to reproduce the error are convenient for reproducing the error, fixing the error and verifying the error.
g) Expected results, describing the results that meet the design requirements.
h) Actual test results, describing the results obtained after the actual test.
i) Necessary drawings to facilitate confirmation of error manifestations and error locations.
(8) Comments such as the tester's suggestion, so that the error handler can quickly and correctly handle the error.
Friends who are doing the test can come in and communicate. The group has compiled a lot of learning materials and interview questions, project resumes, etc....