This series of articles summarizes some common interview questions for software test engineers, mainly from personal interviews, network collection (improvement), daily work discussions, etc. It is divided into the following ten parts for your reference. If there are mistakes, please correct me. If you have more interview questions or pitfalls encountered in the interview, you are welcome to add and share. I hope everyone can find a satisfactory job and encourage each other!
1. Test common problems and procedures
1. Introduce the testing process (emphasis, common!)
Requirements review, test plan, test case , use case review, smoke test, test execution, acceptance test, risk assessment, launch/observation, problem follow-up, test report, review meeting.
Answer based on your own daily experience. The work content of each point needs to be clearly grasped, and it is possible to ask questions about how a certain point works.
2. Introduce the test method
By phase: unit testing , integration testing, system testing , acceptance testing.
By means: black box testing , white box testing , gray box testing.
Other: smoke testing, regression testing.
3. Introduce the test case design method (use case design method & test method need to be clearly distinguished)
Black-box test case design: equivalence class division method, boundary value analysis method, error guessing method, cause-and-effect diagram method, orthogonal test analysis method, process analysis method.
White box testing: statement coverage, decision coverage, condition coverage, condition combination coverage, decision/condition coverage, path coverage.
4. Design a use case for a login page (provide a use case for a certain scenario design, focus!)
Function test : correct input, empty input, character type verification, length verification, whether the password is encrypted and displayed, capitalization prompt, whether the jump page is successful, and log in with another account after logging out.
UI: The interface layout is reasonable, the style is unified, the interface text is concise and easy to understand, and there are no typos.
Performance test : It takes a few seconds to open the login page, a few seconds to click to log in and jump to the home page, multiple clicks, and multiple clicks.
Security: Whether the user name and password are encrypted and sent to the server, the number of wrong logins is limited (to prevent brute force cracking), multiple users can log in from one machine, multiple logins from one user, and check whether the element can see the password.
Compatibility testing: Whether different browsers , different platforms ( Windows , Mac), and mobile devices can work.
Ease of use: Whether the input box can be switched with the tab key, whether the user can log in after pressing Enter, etc.
5. Give an example to illustrate the ability to promote the project (example for personal evaluation)
Example) Promote development to solve the problem that menu permissions need to be logged out before they can be applied.
Description: After the XX project was launched, users were unable to use the old interface due to permission updates + users did not know how to log out to apply the new menu permissions. Many online users reported that relevant functions of the platform could not be used. Solution: remote operation + online guidance for users who have problems to log out, and the script in the early hours of the morning forces users to log out in batches. Push forward: In the next version, push forward the development to deal with the issue of menu permission update, in case users cannot use the function every time the menu is updated. Result: The old interface is still available during user login, and the new menu permissions are not applied until the user logs out and logs back in.
Promote the smoke test: If the smoke fails, the test holds a meeting to list the unreasonable modules and existing problems of the project, and follow up with each person one by one. When the solution is obtained, the follow-up project group explains and everyone in Aite follows up. Test acceptance on time.
Promote document quality: Most of the requirements documents, design documents, and interface documents encountered in daily work are not standardized or detailed. At this time, it is necessary to urge each position to improve their own documents through communication or in the form of bugs.
Combined with my own personal experience, from the problem description + processing process + promotion performance + results, explain one by one.
6. What is the most difficult item encountered in the test? (Master the project on your resume)
XX project: This project is a new project and needs to be connected with a third party. From assisting in testing product modules to changing hands to take charge of the entire project, it has become more difficult to understand the requirements, the order logic is not familiar, and it is difficult to advance the requirements.
In response to these difficulties, in terms of testing: first quickly understand the requirements, and understand the specific progress and test points that need attention with the original test leader. Development: Quickly understand the order logic with developers and the process of connecting with third parties. In terms of products: When encountering a certain demand problem, the product is not accepted, and finally report to the leader + hold a meeting to discuss a better solution. Although there were many problems in the process, through the collective efforts of the project team, the project was finally launched on time.
Explain the project (preferably the project on the resume to facilitate the interviewer to ask further questions). Describe what was difficult + how to deal with it + result.
7. An impressive bug?
Bugs that are hidden deeply, bugs that have a relatively large impact, and bugs that have a tortuous processing process. Describe based on your own experience: how you discovered it, how you dealt with it, the impact, the result, and reflection.
Examples: such as upgrade version compatibility issues, interface security issues, database security issues, server resource occupancy overflow issues, code logic issues, etc.
8. Is your company agile development? Introduce agile development?
Yes, agile rapid iteration, multi-version simultaneous iteration.
Agile development belongs to incremental development. For projects with unclear scope of requirements and frequent changes in requirements, it can respond to and embrace changes to a large extent, advocate simplicity, embrace change, sustainability, incremental changes, and high-quality work , fast feedback, software is your main goal.
9. What are the main contents of the review meeting?
This needs to be illustrated with examples from the project meetings I usually participate in. Such as online bug analysis, optimization and improvement strategy, bug priority, etc.
10. How to test the compatibility of the App , and how to test the interface of the App?
System compatibility (ios, Android), model compatibility (iPhone, Huawei , Xiaomi, Samsung , vivo, OPPO), resolution compatibility, and the software itself is forward and backward compatible.
Interface test: Obtain the interface document, use the fiddler packet capture tool to obtain the request method, url, request parameters, and return parameters of the interface, and then use postman and jmeter to test.
11. What is the difference between Web- side testing and App-side testing (common)
· System structure
Web project, b/s architecture, browser-based; as long as the server is updated in the Web test, the client will be updated synchronously.
App project, with c/s structure, must have a client; if the app modifies the server, all core versions of the client users need to undergo a regression test.
· Compatibility
Web project: a. Browser (Firefox, Google , IE, etc.) b. Operating system (Windows7, Windows10, Linux , etc.).
App project: a. Device system: iOS (ipad, iphone), Android (Samsung, Huawei, Lenovo, etc.), Windows (Win7, Win8), OSX (Mac) b. Mobile phone devices can vary according to phone models and resolutions.
· Performance
Web projects need to monitor response time, CPU, and Memory.
In addition to monitoring response time, CPU, and Memory, the app project also needs to monitor traffic, power, etc.
Compared with Web projects, APP has special tests.
Interference test: interruption, incoming call, SMS, shutdown, restart, etc.
Weak network test (simulation of 2g, 3g, 4g, wifi network status and packet loss); network switching test (reconnection after network disconnection, switching from 3g to 4g/wifi, etc.).
Install, update, uninstall
Installation: Interruption during installation, weak network, deletion of installation files after installation, etc. need to be considered.
Uninstallation: It is necessary to consider whether to delete App-related files after uninstallation.
Update: divided into mandatory update, non-mandatory update, incremental package update, breakpoint resume, update under weak network status.
Interface operation: Regarding mobile phone testing, attention should be paid to gestures, horizontal and vertical screen switching, multi-touch, front and back switching.
Security testing : whether the installation package can decompile the code, whether the installation package is signed, permission settings, such as access to the address book, etc.
Boundary test: less available storage space, no SD card/dual SD card, flight mode, wrong system time, third-party dependence (QQ, WeChat login), etc.
Permission test: Set whether an app can obtain the permission, such as whether it can access the address book, photo album, camera, etc.
Finally, I would like to thank everyone who has read my article carefully. Reciprocity is always necessary. Although it is not a very valuable thing, you can take it away if you need it:
These materials should be the most comprehensive and complete preparation warehouse for [software testing] friends. This warehouse has also accompanied tens of thousands of test engineers through the most difficult journey, and I hope it can help you! Partners can click the small card below to receive