The responsibility of a software test engineer is to find bugs. In addition, how to reflect personal value? Then let us imagine that if we only raise the problem without solving it, the problem will never be closed. Therefore, the basic skills of a senior tester should be this: dig deep into business and functional requirements, find out BUG, locate BUG, and propose solutions. Here we will talk about, when we find a bug, who should submit the bug to solve it, this is a problem of bug positioning.
Imagine:
According to the needs, the user's avatar should be round, but the result is square. Whose bug is it?
When saving user information, it cannot be saved successfully and there is no error message. Whose bug is most likely?
Obviously, we cannot submit these BUGs to the same person for resolution during the work process. We should at least distinguish whether it is a front-end or a back-end bug, just like the popular word "garbage classification". After BUG classification, the efficiency of the entire team will be improved.
1. What is frontend/backend?
At present, most Internet projects are developed separately from the front and the back. So what is the front end? What is the backend? In short, the front-end focuses on page design, and the back-end focuses on service development.
For example, if you want to save a user's information, the front-end displays the interface to the user and allows the user to fill in as needed. When the user clicks the "Save" button, the data will be submitted to the back-end service through the network, and the back-end service will process whether further calculations are required. And save the data in which table in which database.
2. Why distinguish between front-end and back-end bugs?
At present, most projects are developed in collaboration with multiple people. If it is not clear who caused the bug, it is easy to submit to the wrong developer, which will greatly reduce the efficiency of bug resolution.
In addition, if the team is large, or it is assembled by project teams from various regions, it will inevitably increase the communication cost. This requires us to specify who the BUG is when submitting a BUG in a project management software like ZenTao or Jira. Avoid kicking the ball with each other.
Therefore, in order to improve the efficiency of the team, testers must particularly do a good job of classification of BUG.
3. How to locate front-end/back-end bugs?
For an excellent software test engineer, it is particularly important to distinguish whether a BUG belongs to the front end or the back end.
Page request process
before to figure out how to locate and classify BUG, you need to know about the process the page request to http request as an example, the request process is as follows:
the user front page in the operation, such as clicking a feature
page carries the data request, access to specific functions The interface
is executed by the back-end service of the corresponding business logic of the interface. If data is involved, it will request and assemble the data and return it to the front-
end front- end page for rendering and display the corresponding page and data.
What are the characteristics of the front and back BUG?
Front-end BUG
interface related
layout related
compatibility related
back-end BUG
business logic related
performance related
data related
security related
Is there any way to locate the BUG at the front end or the back end?
Here are a few methods that can give you an idea, so that you can understand how to distinguish whether a BUG belongs to the front-end or the back-end during study and work.
Empirical method
Software testers should continue to refine their skills and have more projects in charge, so they naturally have an understanding of the process of function realization and how to classify BUG.
For example:
the resolution of a certain picture on the webpage is incorrect. If we understand the implementation process, we can think that under normal circumstances, the picture is fetched from the server based on a certain address. Generally, the database only saves the address, then the picture can be displayed correctly. The basic function of the back end is to meet the demand. If the specific image resolution is wrong, the most likely cause is an error in the front-end display process.
Log viewing method
When we find a BUG, and we are not sure whether the BUG belongs to the front-end or the back-end, we can check the log of the back-end service. When the BUG is reproduced, check whether there is any relevant information in the log. It can basically be considered that if the log is not output, it is likely that this function does not interact with the backend, and there is no backend problem. On the contrary, if the log has output, you can further check whether there is any error log information for further analysis.
Interface view method
This method is often used to check whether the data returned by the back end to the front end is wrong or the front end shows an error.
Most browsers have their own interface viewing tools. For example, Chrome, FireFox, etc. can enable packet capture via F12, and each http request sent by the current page can be seen in NetWork.
The interface situation seen through Chrome is as follows 
, and the response data can be viewed in Response
We need to compare the data obtained through the back-end interface with the data displayed on the front-end to confirm the problem. If the data is wrong, the page display is wrong, which is also normal. Start with the backend to solve the problem. If the data is correct, but the display is wrong, you need to ask the front-end developers.
Four. Experience and summary
Communication is important
In the process of locating bugs, one of the most important issues we cannot ignore is communication with developers. Sometimes we are busy for a long time, it is better to ask and answer. The growth of experience and technology is also inseparable from reasonable and efficient communication.
Experience and summary
Problems with styles are basically CSS bugs.
Text problems are basically HTML bugs.
Interactive problems are basically Javascript bugs.
Other problems communicate first, then locate
Written at the end:
That's it for today's sharing, and I look forward to everyone's success!