In this article, you will learn how to test Web projects and mobile applications in our company.
Testing is conducted with the purpose to find program errors (bugs) before the users come across them.
We develop projects on the basis of the SCRUM methodology. The testing process is divided into two stages:
[Image Source: https://bit.ly/3SLsnAm]
Testing is carried out by the test engineer. The QA is responsible for the quality of the product released. It’s the QA who makes a decision whether the product is ready to be released or not. The Company has established the standards of mobile app and Web project testing.
To describe bugs we use odoo service. Components of the problem description:
To save time there are certain rules within the team. For example, a bug that has not been played back twice – cannot be placed. If the bug is not created in accordance with the standards, the task may not be accepted.
Depending on the task, the QA specialist chooses the testing type and tools. It’s prepared as a test plan.
Before the testing starts, the QA prepares a test plan which includes:
After the preparations have been done, the QA embarks on playing back of the test cases described in the approved test plan.
Here is a sample of it:
The Website shall correspond to the design and prototype of the Website.
At the moment of the Website handover, the catalog shall correspond to the one that exists in the prototype.
Comments relating to the convenience of the Website usage.
Things that were implemented in the project, but abnormally loading the system.
Download speed of the Website on different resolutions.
We check the Website in all the supported browsers through Browserstack.
We check the Website for the operating speed:
https://pagespeed.web.dev/ , https://gtmetrix.com/, https://www.pingdom.com/
According to the standards, the speed shall be 0.4 seconds.
We check the Website for broken links and broken images:
https://www.drlinkcheck.com/ , https://www.deadlinkchecker.com/
There exist three servers in the project:
The developer works and introduces corrections to the dev server. The QA conducts testing on the test server.