I submitted dozens of resumes on Boss and Lagou, 70% of them were unread, 30% were read, and half of the read replies asked to send attached resumes, and seven or eight companies received interviews this week, so, The current environment is really difficult
In the past half a month, three to four interviews have been arranged every day. On average, each company has at least two rounds of interviews. Orally agreed. I personally like one of the foreign companies. After all, it is not very popular. I am really afraid of domestic Internet companies. The experience of face-to-face technical interviews, I hope it will be helpful to everyone, come on! rush!
technical interview questions
1. Project and business related
1. Please describe the testing process in your current project ?
Requirements presentation-->Requirements review-->Technical review-->Test case review-->R&D smoke-->R&D test-->Test test pre-check.->Test lane test.>Release shuttle bus.. >Test integration test (product acceptance)->pre-release environment release-->production environment release (product test acceptance)-->online data monitoring (1-2 days)-->business document precipitation (this is the case in our company, Everyone can explain according to the actual situation)
2. Is there anything that can be improved in the testing process? Do you have feedback on these issues and get the results?
1) Standardize the publishing process, during the Tuesday-Thursday window period, bi-weekly iterations of the APP category, and recover the R&D online publishing authority;
2) Standardize the test submission process, increase the admission conditions for test submission, the test submission and return process, and the penalty mechanism for failing to pass the smoke;
3) Standardize product review, new demand presentations, product completion of more than 90% will enter the review, and demand completion will be rejected;
4) Introduce the online CS mechanism, PO, P1 old hospital replay, P3, P4 CS precipitation, record the experience of stepping on the pit, reverse process optimization or basic function construction.
3. The demand is not clear, how to solve it?
1) The fundamental problem is the process mechanism. Teamwork cannot rely on the reliability of individuals, but requires a process mechanism to establish. The person in charge and the way of collaboration are two indispensable elements for the operation of the mechanism. The establishment of process mechanism can also refer to agile and lean thinking.
2) Make a breakthrough in communication. The high-quality and timely delivery of the project is the common goal of the industry and research. From the common goal, communicate and solve the problems in the cooperation.
4. There are too many test tasks and not enough time, what should I do?
Individual project questions:
Whether the test scope is incomplete evaluation, resulting in overly optimistic time estimation, and the man-hour ratio of time estimation, R&D and testing is 3:1 (plus time)
Whether there is a problem blocking the test progress (bug, test environment , etc.), taking up the test time and reversing the project, there are many functions, and the test time is insufficient (cut demand, go online in batches) 2) Most of the project problems
Whether there is a problem with test efficiency, whether there are too many redundant test cases
Whether there are often parallel tests, causing the test performance to fail to meet expectations (resource allocation)
· The long-term personnel load is greater than 80%, whether the task arrangement is reasonable, and whether the manpower reaches the bottleneck (adding people)
5. Introduce the difference between cookie, session and token
1) The session is stored in the server, which can be understood as a status list, with a unique identification symbol sessionId, which is usually stored in a cookie. After the server receives the cookie, it parses out the sessionId, and then searches in the session list to find the corresponding session.
2) A cookie is like a token with a sessionId, stored on the client, and the browser usually adds it automatically.
3) cookie security is worse than session.
4) The token is also similar to a token, stateless, user information is encrypted into the token, and the server can know which user it is after decrypting it after receiving the token.
6. The difference between Get and Post requests
1) get is to get data from the server, post is to send data to the server.
2) The parameters of get can be seen in the URL, but the parameters of post cannot be seen by users.
3) The amount of data transmitted by get is small and cannot exceed 2KB. The amount of data transmitted by post is relatively large, and it is generally defaulted to be unlimited.
4) The security of get is relatively low, and the security of post is relatively high.
7. What are the common status codes?
2 represents success;
200: The request is processed normally. 3 means redirection;
301: Permanent redirection, the resource has been assigned a new URI;
302: Temporary redirection, the resource has been temporarily allocated a new URI4 represents a client error;
400: Request message syntax error, or parameter error 401: Need to pass HTTP authentication, or authentication failed 403: Request resource rejected;
404: The requested resource could not be found, and the server rejected it for no reason. 5 represents a server error;
500: internal server error;
501: The request was not completed. The server does not support the requested function 503: The server is overloaded, or it is down for maintenance.
8. What is the difference between HTTP and HTTPS?
1) http is a hypertext transfer protocol, information is transmitted in plain text, and https is a secure ssl encrypted transfer protocol.
2) http and https use completely different connection methods and different ports, the former is 80.
9. How to troubleshoot whether it is a front-end problem, a back-end problem or a data problem?
1) Confirm whether the front-end calls the interface by capturing packets. If the interface is not called, then there is a problem with the front-end.
2) If the interface returns the result normally, but the result is not the expected result, check whether the front-end parameters are correct. If the parameters are incorrect, it is a front-end problem. If the parameters are correct but the result returns an error, it is a back-end problem.
3) If the data returned by the backend interface is correct, but the page is displayed and rendered incorrectly, this is also a frontend problem.
10. Differences between Web testing and APP testing
1) The mobile phone is used as a communication tool. Operations such as incoming calls, outgoing calls, and receiving text messages will have an impact on the app application program. Therefore, the first attribute characteristics to be considered in the app test are: interruption test, incoming call interruption: call hang up, call hang up Disconnected, call hung up, call interrupted by hangup message: receive text messages, view text messages.
Other interruptions: Bluetooth, alarm clocks, plugging and unplugging data cables, phone locks, phone power outages, phone problems. (system crash, reboot)
2) Mobile phone users' installation and uninstallation of app products: directly upgrade from the previous version/two previous versions to the latest version.
· Fresh install the new version
The new version overwrites the old version, install and uninstall the old version, install the new version, uninstall the new version, and install the new version
· There is no difference between web and app testing in terms of functional interface testing. The main differences are the following points:
1. System structure
The web side is based on B/S architecture. If the server side is modified, the client side will be updated synchronously.
The app is a C/S architecture. If the server is modified, the client must be updated, and the core version of the client must be re-tested.
2. Performance indicators
Web side: Response time, CPU, memory, throughput.
app: Response time, CPU, memory, throughput, mobile traffic, mobile power.
3. Compatibility testing
web side: browser compatible
C-side operating system. (windows, mac, linux)
app: mobile phone operating system (Android, ios, windows); phone model; resolution. (Mobile screen size)
4. Compared with the web, the app has some special tests for interference testing (incoming calls, messages, other applications) weak network testing, network switching testing installation, update, and uninstallation.
5. Test tool app:appium web:selenium
6. Interface operation
Web side: upper left corner and lower right corner of the screen.
app: Gestures, mobile phone horizontal and vertical screens, touch, front and back switching, corner test.
11. What indicators should performance testing focus on?
1) Response time (RT): Response time refers to the time it takes for the system to respond to a request.
2) Throughput (Throughput): Throughput refers to the number of requests processed by the system per unit time.
3) Concurrent number: The number of concurrent users refers to the number of users who can normally use system functions that the system can carry at the same time.
4) OPSueries Per Second means "query rate per second", which is the number of queries that a server can respond to per second, and is a measure of how much traffic a specific query server handles within a specified time.
5) TPS: It is the abbreviation of TransactionsPerSecond, which is the number of transactions that a server can process per second. It is a unit of measurement for software testing results. A transaction is a process in which a client sends a request to a server and the server responds. The client starts timing when it sends a request, and ends timing after receiving the server's response, so as to calculate the time used and the number of completed transactions.
12. How does your company do interface testing ?
The actual difference between interface testing and general testing is the design part of the test case.
1) Obtain the interface specification.
2) Design interface test function use cases (mainly from the perspective of users to see whether the interface can meet business requirements, use case design is the set of black box use cases).
3) Verification of various input parameters (normal conditions, abnormal conditions include incorrect number of input parameters, incorrect types, optional/mandatory, and consideration of mutually exclusive or related parameters).
4) Various verifications of the interface return value. (meet interface documentation requirements)
5) Understand the interface implementation logic and realize logic coverage. (statement/condition/branch/judgment/...)
6) Can the interface be executed concurrently, is it safe, and does the performance meet the requirements?
7) Use tools or self-written code to verify.
8) The problem found is the same as the functional test, the bug should be reported, and the tracking status of the tracking status should be tracked.
13. How to design interface test cases?
Generally, the following aspects need to be considered when designing interface test cases:
① Whether the prerequisites are met.
Some interfaces need to meet the prerequisites to successfully obtain data. A common reverse use case that needs to log in Token: Design 0~n use cases for whether the preconditions are met (assumed to be n conditions).
②Whether to carry the default value parameter.
Forward use case: None of the parameters with default values are filled in, no parameters are passed, all required parameters are filled with correct and existing ""regular" values, and others are not filled in, and one use case is designed.
③Business rules and functional requirements.
Here, according to the time situation, combined with the interface parameter description, it may be necessary to design N positive use cases and detailed thinking cases.
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