foreword
As a software test engineer, whenever you change jobs, you will inevitably encounter some "send propositions" in the interview. The reason why these questions are called "send propositions" is mainly because of them: some knowledge points are easy to confuse; some questions are difficult to answer to satisfy the interviewer; some questions are even beyond their own cognition...
[The article finally organizes the interview questions of software testing companies for everyone]
Based on this, we will answer your questions from time to time, and summarize these trivial knowledge points to facilitate your memory.
1. If you were given a website, how would you test it?
(PS: Regarding this issue, I believe that everyone has encountered it in many technical interviews. However, there are still many friends who leave a message saying that their description is not clear, or that they forget the steps when they are nervous. I will sort them out for you today. once.)
The first step is to find the requirement specification, product description, design document, etc., and analyze the test requirement points one by one;
The second step is to formulate a reasonable test scope, test strategy and implementation plan through requirements analysis.
The third step is to design test cases. We can design use cases in a targeted manner by decomposing the test content. for example. If we want to do functional testing, we need to test links, media elements, interfaces, page layouts, plugins, text, etc. including but not limited to:
Whether the link jumps correctly;
Whether there are empty pages and invalid pages;
Whether there is an incorrect error message returned;
Whether the page style is uniform and beautiful;
Whether multimedia elements can be loaded normally;
Whether the controls are used normally;
Whether the page layout is reasonable, whether the key content and hot content are prominent; and so on.
2. While testing a project, you found a system bug, but the developer didn't think it was a bug. How should you solve this situation?
A: First of all, in the attitude of solving the problem, communicate with the members of the development team again. If the other party still thinks that this issue can be ignored, and I still feel that it is necessary to investigate further, then I will deal with it as follows.
First, document the problem. Fill out the bug list and submit it to the defect management library;
Secondly, through the software requirements specification, product description, design documents, etc., to identify the basis of defect judgment. Here are the main things to note:
1) Is there any discrepancy between the actual results and the expected results;
2) If there is no basis for judging bugs in the above instructions, we can consider whether it is a defect based on past experience and the general characteristics of similar products. Or judge from the user's point of view;
3) Whether it is possible to fully discuss and draw conclusions through designers or users;
4) If the above three methods do not work, you can objectively and rationally describe your views on this issue to the test manager, and let the test manager measure the severity of the problem. If the test manager can't judge, you can also react to the company's decision-making level and let them decide how to deal with the problem.
3. If you want to do a security test for the APP, which aspects should be tested?
Regarding this issue, first of all we have to make it clear that different systems have different security indicators. We should adjust the testing strategy according to the system security indicators. Software security testing mainly includes two parts: program and database. From this, our test plan is roughly as follows:
1) When dealing with user authentication security issues, the main issues we need to consider are:
Whether the permissions of different users in the system can be clearly distinguished;
Whether there will be conflicts between users in the system;
Whether there is a loophole in the user's login password, whether it is visible and copyable, and whether there is a "universal password" due to a special string;
Whether it is possible to log in to the system through absolute means (in short, whether it is possible to directly enter the system by copying the link of the user's login page);
Whether the user can use the back key to enter the system without entering a password;
Whether users can delete footprints (including account passwords, browsing traces, caches, etc.) after logging out of the system;
2) When dealing with system network security issues, consider the following issues:
Whether the protection system is strong when attacked by unauthorized users;
Use mature network vulnerability inspection tools (ie: professional hacking tools, such as NBSI series and IPhacker IP, etc.) to check whether the system has relevant vulnerabilities;
Confirm whether the system patches are ready and whether the system protection measures are installed;
Use various types of Trojans to confirm whether the system Trojans are in good condition;
Use various anti-plug-in tools to confirm whether there are plug-in loopholes in each group of programs in the system, etc.
3) Database security considerations:
Confirm whether the system data is independent and manageable;
Confirm whether the system data is complete;
Confirm whether the confidentiality of the software system like a bank is good;
Confirm whether the data can be backed up, whether it can be restored, etc.
4. What is a test case? What is a test script? What is the relationship between the two?
1) Test case
In simple terms, a test case is a set of conditions or variables, which is a specific set of input data, operations or various environmental settings and expected results provided to the system under test in order to implement the test. Testers use it to determine whether a software or system is working properly.
For different test projects, we need different test cases to ensure the smooth progress of the project.
The basic elements of software test cases, including: use case number, test title, importance level, test input, operation steps, expected results. some of:
Case numbering: There are certain rules for the numbering of test cases. Because the main purpose of its existence is to facilitate the search, and facilitate tracking.
Test Title: It is a description of the test case and is used to clarify the purpose of the test case. For example, test how the software responds when a user logs in with an incorrect password.
Importance level: Define the priority level of test cases, which can be broadly divided into two levels: "high" and "low". In practical work, we generally divide it into 5 levels.
Test Input: Provides various input conditions in test execution. It should be noted here that the input of the test case has a great dependence on the input of the software requirements. If there is no well-defined requirement input in the software requirements, then the test case design will encounter great obstacles.
Action Steps: Provides the steps of the test execution process.
Expected Result: Provides the expected result of the test execution. Expected results should be concluded based on the outputs in the software requirements.
2) Test script
A test script generally refers to a series of instructions for a specific test. These instructions can be executed by automated testing tools. Test scripts are computer-readable instructions that automate the execution of a test process (or portions of a test process). Test scripts can be created (recorded) or automatically generated using test automation tools, or programmed in a programming language, or a combination of the first three methods.
3) The relationship between the two
Simply put, a test script is the part of the automated test in the test case. The writing of the script must correspond to the corresponding test case.
5. What is your greatest interest in testing? Why?
This question is asked in almost all test interviews. There is no fixed answer to this question, and everyone can express it according to their own understanding and sense of substitution. But it is worth noting that the answer must be sincere, in line with your own personality, and don't let others think you are hypocritical or self-righteous.
Below are some interview questions from software testing companies, you can click here to get them .
