#####This article is based on the test questions of some students on the Internet. If there is any infringement, please contact me to delete it.
1. How to submit high-quality BUG
1) First, before submitting this BUG, it has been reproduced online and in the test environment, and other problems caused by it have been sorted out, and the reasons and types of its occurrence have been analyzed. If you have the ability, you can propose amendments,
2) The second thing is to pay attention to the BUG submission. The first is validity. Ensure that the submitted BUG clearly belongs to a certain module that has been set. Ensure that you clearly understand the requirements, prerequisites, and input data. BUG is the only one. Avoid submitting BUGs caused by operational errors, or BUGs that have already been submitted.
3) The content of the submission. The title should be concise and clear, and you will know what it is at a glance. BUG test environment, version, and test equipment. The specific BUG description, as well as the effect required by the requirements, and the specific test steps generated by the BUG, the exact point, a few clicks, and the data. Allow developers to quickly make changes based on the information you provide.
4) Assigned to the developer who needs the bug
2. What are the aspects of writing test cases?
Project name, project version, test environment, module name to which the use case belongs, function points, use case number, use case level, preconditions, specific test steps, expected results, actual results, and reasons for failure.
3. The difference between session and cookie
http is a stateless protocol (refers to the protocol has no memory capacity for transaction processing. Lack of state means that if the previous information is needed for subsequent processing, it must be retransmitted, such as the client closes the browser after obtaining a web page, and then starts it again Browser, log in to the website again, but the server does not know that the client closed the browser once) and Session and Cookie are two mechanisms proposed to solve this problem.
cookie: Cookie is actually a short piece of text information. The client requests the server. If the server needs to record the user's status, it uses the response to issue a Cookie to the client browser. The client browser saves the Cookie. When the browser requests the website again, the browser submits the requested URL together with the cookie to the server. The server checks the cookie to identify the user's status. The server can also modify the content of the cookie as needed. Cookies allow the server program to track each client's visit, but each client's visit must return these cookies. If there are many cookies, this invisibly increases the amount of data transmission between the client and the server.
The emergence of session:Session is precisely to solve this problem. Every time the same client interacts with the server, it does not need to return all the cookie values every time. Each user accesses the server to establish a session. How does the server identify the unique identity of the user? In fact, when the user establishes a connection with the server, the server will automatically assign a SessionId to it, and each client is unique.
Differences: 1) Cookie determines the user's identity by recording information on the client side, and Session determines the user's identity by recording information on the server side. 2) Cookies are a kind of Session object. But there are differences. Cookies do not occupy server resources. They are stored in the client memory or a cookie text file; while "Session" will occupy server resources. 3) The storage of cookies limits the amount of data, only 4KB is allowed, while session It is unlimited 4) We can easily access the cookie value but we cannot easily access the session value, so it is more secure.