Preliminary analytics during website testing: Difference between revisions
(Created page with "Preliminary analytics during website testing") |
No edit summary |
||
| Line 1: | Line 1: | ||
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. | |||
Revision as of 16:29, 6 July 2023
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.