Preliminary analytics during website testing

Preliminary analytics during website testing

Errors, which were found during the testing of the website, can have different types of sources.

Therefore, QA Analysts should conduct preliminary analytics of the source of the error independently and clarify the type of the error for further optimization of the time for its elimination.

Types of the errors (bugs, glitches)

To investigate the bug, testing is recommended to be done with the browser developer tools (usually opened by pressing F12 or right-clicking on any page and selecting the "Inspect" option in the menu that opens).

The environment, in which the bug was detected, should be attached to the bug report (for example, for desktop – Windows/ Mac, mobile - Android / IOS and its version), browser type and version.

If a big is found, check:

- whether the software bug is repeated after a full reload of the page;

- clear cache, browser cookies, check in incognito mode;

- if the error occurs on a specific environment (browser, browser sizes, OS), note it in the bug report.

To whom to address bug reports of various types of errors

All errors should be assigned to the development team (in the Redmine, this is the IT Development group (for Bloomex sites and its admin panels, Chatbot, Mobile application, Mailbot, etc) or the Poltavsky team (projects are listed in table № 3) and select the appropriate category according to the table № 1 and 2.

In case of a server error (site is unavailable) – immediately inform the admins.

Table № 1

Categories of bugs

Bug type, short description	Characteristics	Recommended actions of the QA Analyst
Software error in the application (Functional bug). Whenever some mechanism does not work properly, it is most likely a bug in the application code.	●               the application generated an error message; ●               the application “hung”, the current state of the active window (widget, form) does not change in any way through the interface; ●       the expected result of the user's action does not occur for no apparent reason;	●     Take a screenshot/video of the error, or save its full text. ●     Save the text of the first (top) error in the developer tools console. Save the network data of the last server response. Use for convenience filtering requests by type Fetch / XHR, pay attention to requests like myCoolSite.ca/api/…
Data errors (Content bug) Something is not displayed, or something is not displayed as expected.	●     no errors in the console ●     no image, menu item, title or piece of text is displayed ●   there is a list, but it is empty	●     Take a screenshot/video of the error ●     Indicate a suspicious place on the screenshot ●     Describe in text what is expected at that location