My friend secretly told me the interview questions after the interview. To get an offer, you must have a solid basic skills!
1. Please describe how to classify the severity and priority of defects and errors?
The general principles for categorizing the severity and priority of software defects and errors:
(1) Represents the hungry hazard and severity caused by software defects.
(2) Priority indicates the importance and order of repairing defects.
Priority:
(1) Highest priority: Repair immediately and stop further testing.
(2) Second highest priority: must be repaired before the product is released.
(3) Medium priority: It should be repaired if time permits.
(4) Lowest priority: may be fixed, but may also be released.
Severity:
(1) Serious: system crash, data loss, data corruption
(2) More serious: operational error, result error, missing function
(3) General: minor problems, typos, UI layout, rare failures
(4) Suggestions : Does not affect the use of flaws or better realization.
2. What phases should a complete test consist of? Explain each stage separately.
A complete test should consist of five stages:
1. Test plan
First, define the corresponding test requirement report according to the specifications of the functional requirements and performance indicators in the user requirement report, that is, formulate the highest standard for black box testing. All future testing work will be carried out around the test requirements , The application program that meets the test requirements is qualified, otherwise it is unqualified; at the same time, the test content should be appropriately selected, and the test personnel, test time and test resources should be reasonably arranged.
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 choice of test cases will directly affect the test results Validity).
3. Test development
Establish a reusable automatic test process.
4. Test execution
Execute the automatic test process established in the test development stage, and track and manage the defects found. Test execution generally consists of unit testing, combination testing, integration testing, system joint debugging and regression testing. Testers should take a scientific and responsible attitude to conduct tests step by step.
5. Test evaluation
Combined with the quantitative test coverage and defect tracking report, comprehensive evaluation of the quality of the application software and the work progress and efficiency of the development team.
3. What is recorded in a software defect?
1. The general UI should be unified and accurate
. The UI of the defect report should be consistent with the UI of the tested software, so that it is easy to find and locate.
2. Try to use the usual expression terms and expression methods in the
industry . Use the usual expression terms and expression methods in the industry to ensure accurate expression and professionalism.
3. Each defect report includes only one defect.
Each defect report includes only one defect, which enables the defect fixer to quickly locate a defect and concentrate on correcting only one defect at a time. The verifier only verifies whether one defect has been corrected correctly at a time.
4. Non-reproducible defects should also be reported.
First, the defect report must demonstrate the ability to reproduce defects. Defects that cannot be reproduced shall be reproduced as far as possible. If the defects cannot be reproduced after doing their best, the defect shall still be reported, but the frequency of occurrence of the defect that cannot be reproduced shall be indicated in the report.
5. Clearly indicate the type
of defect According to the phenomenon of the defect, summarize and judge the type of defect. For example, that is, functional defects, interface defects, and data defects. Reasonable suggestions are the most common type of defects or defects, and other forms of defects or defects are also subordinate to one of them.
6. Clearly indicate the severity and priority of the defect.
Always specify the difference between the severity and priority of the defect . Highly serious issues may not be worth solving, and small cosmetic issues may be considered high priority.
7. Description (Description), concise, accurate, and complete, reveal the essence of the defect, record the defect or the location where the defect appears, The
description should accurately reflect the essence of the defect, short and clear. In order to find the specified test defects in the software defect management database, it is a good habit to include the user interface (UI) when the defect occurs. For example, record the title of the dialog box, the name of the menu, button and other controls.
8. Use automatic digital serial numbers between short lines, use the same font, font size, and line spacing between
short lines, use the same font, font size, and line spacing to ensure that the format of each record is consistent and standardized profession.
9. Try to record only one operation for each step to
ensure that it is concise, organized and easy to repeat the operation steps.
10. Confirm that the steps are complete, accurate and short. To
ensure rapid and accurate repetition of defects, "complete" means no omissions, "accurate" means correct steps, and "short" means no redundant steps.
11. According to the defect, you can choose whether to capture the image.
In order to visually observe the defect or defect phenomenon, it is usually necessary to attach the defect or the interface where the defect appears, in the form of a picture as an attachment attached to the "attachment" part of the record. In order to save space and truly reflect the defect or the nature of the defect, the full screen, active window and partial area of the defect or defect can be captured. In order to quickly locate and correct the defect or defect location, it is usually required to attach a Chinese map.
Attach necessary special documents and personal suggestions and comments.
If a defect or defect occurs when a particular document is opened, the document must be attached so that the defect or defect can be quickly reproduced. Sometimes, in order to make the defect or the defect fixer further clarify the defect or the manifestation of the defect, it is possible to add personal suggestions or comments for modification.
12) Check spelling and grammatical defects
Before submitting each defect or defect, check the spelling and grammar to ensure that the content is correct and the defect is described correctly.
13) Try to use phrases and short sentences to avoid complex sentence patterns
. The purpose of the software defect management database is to facilitate the location of defects. Therefore, objective descriptions of operating steps are required, and no modified vocabulary and complex sentence patterns are required to enhance readability. Sex.
4. Briefly describe the life cycle of the defect.
Open: Indicates that the problem is submitted to be processed by someone.
Re-assignment: The problem is reassigned to someone to deal with.
Processing: The problem is being processed and not yet completed.
Fixed: Confirm that this problem exists, but will not handle it temporarily.
Regression: Regression confirmation for the fixed problems. Reopened:
Closed: The last state of the problem.
5. What are the test case design methods?
1. Equivalence class division method, as the
name implies, equivalence class division is to divide the test range into several disjoint subsets, their union is the complete set, and several representative values are selected from each subset As a test case.
2. Boundary value analysis method
Long-term test work experience tells us that a large number of errors occur on the boundary of the input or output range, rather than inside the input and output range. Therefore, by designing test cases for various boundary conditions, more errors can be detected. The selected test case should be a value that is exactly equal to, just greater than, and just less than the boundary. For example, for the value in the interval min, max, the test case can be recorded as min, min+, max, max-.
3. Wrong speculation method
Wrong speculation method refers to: when testing a program, people can guess various errors that may exist in the program based on experience or intuition, so as to write targeted test cases to check these errors.
4. Judgment table method
Also known as the strategy table, the test based on the strategy table is the most rigorous test method in the function test. This method is suitable for scenarios with complex logical judgments. The results are obtained through exhaustive conditions, and then the results are optimized and combined to obtain a clear judgment strategy table.
5. Orthogonal experiment method
Using language to describe the orthogonal experiment method is very abstract and difficult to understand. Simply put, it is to design a special table under the condition that each factor is independent of each other, and find a small number of alternative test cases .
Among them, the special table mentioned above is an orthogonal table, which is a table generated according to certain rules.
Although it is a special table, the actual form of expression is no different from the general table. The main feature of the orthogonal table is that it is "evenly distributed and uniform". It is precisely because it is "even" that it can replace all with a few.
6. A text box requires a 6-digit password, and only three input errors are allowed for each account at a time. What are the equivalent intervals for testing and designing this text box?
1. Password is empty to log in
. 2. Enter correctly (enter the correct value) login
3.
Enter incorrectly (enter the wrong value, enter data such as special symbols, English letters, Chinese characters and illegal characters and other incorrect values; input methods such as : Less than six digits, more than six digits, maximum input value) Login/Cancel
4. Enter more than three consecutive incorrect entries (check the prompt information and results after consecutive incorrect entries)
5. Others (do you support clipboard operations, such as: copy/cut Cut/paste)
7. When will the performance test start?
Performance testing is generally divided into pre-stage and post-stage.
The early stage is the system integration period after the function is realized. Performance test can be performed for function realization to see the response time of individual function realization
The later stage refers to the overall performance test stage after the system function has passed the functional test.
8. What are performance testing, load testing, and stress testing?
Performance Test (Performance Test): usually collects all the performance related to the test, and is used by different people on different occasions. Focus: how much and how fast
Load Test (Load Test): Load test is a kind of performance test, which refers to whether the data is running in an overloaded environment and whether the program can bear it. Focus: how much
Stress Test (Stress Test): Stress test (also called stress test) is also a kind of performance test. It operates under the condition of extremely low system resources. The purpose is to find out where and how the system fails.
9. Briefly describe the steps of
Loadrunner. Use LoaderRunner to perform several steps for performance testing:
a. Develop scripts (executed in Vugen): involving script recording, parameterization, transaction addition, checkpoint setting, synchronization point Set up. The loaderRunner script conforms to the C language syntax.
b. Scene establishment (executed in Controller): add script (if there is a rendezvous in the script, the rendezvous should take effect here) and user settings.
c. Analysis of test results.