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
Functional bug. Software error in the application. 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/…
Content bug. Data errors. 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
Layout bug. Visual inconsistencies in app design.	●     no errors in the console ●     font, color, padding, and/or other visual cues that do not match expectations	●     Take a screenshot/video of the error ●     Indicate a suspicious place on the screenshot ●     Describe in text what is expected at that location
UX bug. User experience bug	●   inconvenience/ illogicality of working with elements/ functionality of the page	●     Take a screenshot/video of the error ●     Indicate a suspicious place on the screenshot ●     Describe in text what is expected at that location
Undefined bug.	●   If there is difficulty identifying the type of bug	●     Take a screenshot/video of the error ●     Indicate a suspicious place on the screenshot ●     Describe in text what is expected at that location

Table №2

Common mistakes and recommendations for analytics

Description of the problem	Actions to identify the source of the bug	Bug category
The image is not displayed	If instead of an image a default browser box is shown for an unloaded image - check the link to the image using browser developer tools. If there is a link, but it does not open - save it in the bug report and interpret it as an application error.	Functional bug
	If there is no link to the image, then it was not uploaded - this is a data management error. If a dummy image is published instead of an image, this is a data error. The image was not loaded in the admin panel.	Content bug
Order payment failed	You entered obviously correct card data on the prod version of the site, but after trying to pay an error occurred. It all depends on the text of the error. If it says that the payment was declined, incorrect card details or something like that, it means that everything is working correctly from the application side, but the payment system rejected the payment for some reason. The developers cannot solve this issue. You need to contact the responsible employees, who deal with the issue of the payment system or the cardholder. ●          In all other cases, if there is a payment error, contact the developers. ●          Errors in entering card data into the form are not handled correctly - contact the developers. ●         Instead of a message about successful payment, any strange error or freeze - contact the developers.	Functional bug
Google address autocomplete shows a weird error instead of an address hint	Something happened to the service authorization key.	Functional bug
You see in the site interface something like iface.itemLabel	It is an error in the localization file.	Functional bug
When changing the country in billing or shipping, the corresponding list of states is not pulled up and (or) a number is displayed instead of the state name	It is an error in the directory.	Functional bug
Fewer countries are available in billing than expected when placing an order	It is a data an management error. Management of countries from where payment is possible for a particular site is done through the administration system.	Content bug
The list of states suggests fewer states than there are in the selected country when placing an order in billing.	It is a data an management error. Billing staffing for a particular site is managed through the administration system.	Content bug
The list of states suggests fewer states than there are in the selected country when placing an order in shipping.	Maybe it's not a mistake Some sites that serve local physical flower shops specifically list a limited list of shipping states. Check with the staff responsible for the sites.	Content bug
Empty category: there are no products in the list on the site	It is data management error. You should get attention to site managers that they have an empty category. Let them remove it from the category tree or add products there.	Content bug
Empty category: there are no products in the list on the site	It is data management error.	Content bug
There is a link to the document, it opens, but it is completely empty	It is data management error. It is likely that for this site in this language they forgot to fill in the content of the document.	Content bug
The website layout is displayed incorrectly	Layout error is a consequence of an error in the markup (HTML) or styling (CSS) of a page element in a specific environment (for example, an adaptive design problem: an element is displayed on one mobile device, but not displayed on another, elements overlap each other friend, etc.)	Layout bug
Inconvenience / illogicality of working with elements / functionality of the page	For example, it is not possible to click on the X button the first time, the order is deleted after clicking on the X button)	UX bug

Table №3

Poltavsky team projects

	dev	dev v2
florist.ca		dev2.florist.ca
bloomex.co.nz		dev2.bloomex.co.nz
fleurconcept.com		dev2.fleurconcept.com
mannflorist.com		dev2.mannflorist.com
fleur-quebec.com		dev2.fleur-quebec.com
rollasonflowers.net
fortfloralshop.com
lottiejonesflorist.ca
burkittsfloral.ca
blossomshop.ca
milbankeflowers.ca
lancasterflorist.ca
reddeerfloral.ca
Thingsengraved
thingsengraved.ca		vue-front-2.necs.ca
Admin panel
adm-eu.necs.ca	dev1.product.bloomex.ca
Authorization service
api-users.necs.ca	dev1.api-users.necs.ca
Media container
live.data.necs.ca	dev1.data.necs.ca

In the future, the bug is analyzed by the PM and assigned to the appropriate specialists, if necessary.

Table №4

Website Managers

Bloomex Canada	Mark Camphaug
Bloomex USA	Mark Camphaug
Bloomex Australia	Robert Boban
Retail sites (noted in adm-eu.necs.ca)	Kaley Boschma