How we keep high quality standards at SapientPro

02 Jul 2019
Ihor, back-end developer
If you want to build a successful project, it is important to realize that testing is as crucial as development itself.
all news

When it comes to money, we all want to have the best quality at the most affordable price. However, it is common knowledge that the better the quality, the higher the stakes. If being penny wise and pound foolish is not your case, read this article and find out about the quality standards we boast at SapientPro.

In order to assess the quality of a product, one should take into account certain benchmarks. What is essential in our field for the best performance and efficiency is diligent testing and the lack of bugs. Continuous examination of the product is a key to success and the remedy for possible this-thing-does-not-work splitting headaches. Let’s take a closer look at various types of software bugs, product testing and why these things matter.

Product testing is a search of software bugs. What bugs may crawl in particular?

Types of software bugs


Critical (showstoppers) — these bugs block a part of the functionality or business logic, thus making a user unable to use the product. The absence of navigation to some parts of the functionality is also considered to be a critical bug.

Another example is when the app crashes and stops working completely or when a user gains access to some parts of the functionality which are not meant for the user with this access level. Other examples of critical bugs include problems with adding a publication when it is not added to the database and the data are lost; difficulties with registering or logging in to a website and other painful user experience.

Major — primary functions work well but secondary ones don’t. For instance, the program sends the mail but it does not show the message statistics. Or when there is an option to upload a profile photo but a user is unable to do it. In general, this bug doesn’t affect the business logic but you still wouldn’t want to have it.

Minor — you should have an eagle eye to notice these bugs as they have no impact on the functionality. For instance, a part of the text has a different translation or a user’s photo size is smaller than minimum. This bug does not have an influence on the business logic, thus being non-critical.

Trivial bugs include typos in the texts of the buttons, a text block exceedings its boundaries, an image out of alignment or other small design errors. These software bugs are the easiest ones to identify. They have no impact on the functionality.

Product testing is…


Basic — after a developer completes introducing new functionality, it is tested for critical/blocking and major bugs. Before the code goes to stage server, the developer fixes all reported bugs.


Advanced — at the end of each sprint QA engineers test the new functionality, checking the business logic as well as UI/UX. It goes without saying that all reported bugs should be fixed and the product — retested.

All critical or major bugs should vanish into thin air after these two types of software testing. For many startups, this is the final testing point, especially at the proof of concept stage.


Test automation — automated tests are used for large-scale and complex projects. In this case, there is usually a big team working on one and the same project, so changes in one part of the project can lead to critical bugs in another one. While manual testing may be time-consuming, automated tests can be run quickly and perform as much work as one manual tester does during the whole day. As a result, it is also cost-efficient and effective.


Why is testing so important?


Errors are inevitable in any project. Although it cannot be an excuse for your product’s malfunctioning, even such tech giants as Microsoft, Facebook or Google, where thousands of IT professionals work, have software bugs every now and then. Some of these bugs have become legendary.

If you want to build a successful project, it is important to realize that testing is as crucial as development itself. While testing the product, we do our best to fix as many bugs as possible before the product goes live. Sooner or later the bugs will become noticeable and troublesome — for you and for your clients. Critical bugs can even result in losing your clients and affecting your reputation in a negative way.

SapientPro wants our customers’ businesses to grow and develop. The more successful our customers are, the more successful we are. We do what it takes to offer you high-quality services and state-of-the-art products.

share this article in:
Footshop visiting us in Chernivtsi
Ihor, back-end developer
Footshop visiting us in Chernivtsi
read more
© 2023 SapientPro. All rights reserved.
career design typing career design typing Ресурс 1