Back to blog

Am I launching my digital project? The art of technical performance testing, don't miss any bugs

Thomas Huber

July 1, 2020

8 min of reading


Have you finished designing and developing your entire digital project, are you ready to go? Be careful not to go too fast. Have you already did a technical performance testing on your product?

Technical performance testing validation is an essential phase when launching a digital project. Too often, project leaders neglect this step, to get their website or application out as quickly as possible. However, not testing your product wastes money, quality and time. Why? No one is perfect, neither is your product. Following too fast releases into production, some bugs appear and ruin the user experience.

What is a technical performance testing?

This is a test or series of tests, intended to validate the functioning of your digital product and its compliance with the specifications.

During the acceptance, each step of the project, each functionality must be tested and validated. You need to check that your product is working properly. It's not about putting a page on a screen, but making sure everything behind it is up and running. Then you need to analyze the compliance against your specifications.

The recipe phase is an incredibly important part when developing an app, but some developers underestimate it. The problem is that the risk of a bug occurring increases with each line of code, and the costs of fixing bugs increase over time. However, with a properly tested website or application, none of this should happen. So if the app test goes smoothly, the app is ready to be released.

The more media, the better

To successfully complete your recipe, it is important to test your product on different media. Operation is very different from browser to browser, and some bugs can be found and not others. For example, if you launch your mobile application, you must test it on Android and IOS, and to go further you must also test it on several models of mobile: Iphone 11, Iphone 5, Samsung A7… Of course at the beginning of your project, you will not have access to all the technological resources for your recipe, but try as much as possible to test your project on all the mobiles you have at your disposal.

The same goes for a website, developers should perform browser compatibility test to check if your website displays correctly on different browsers. Another test to be performed is the Mobile Browser Compatibility Test which, as the name suggests, is supposed to confirm that the app displays correctly on different mobile browsers. Different operating systems display certain items differently. This is why it is important to perform compatibility tests with as many operating systems as possible, especially the most popular ones such as Windows, Mac, Linux, as well as with various popular browsers such as Chrome, Internet Explorer, Safari, Firefox, etc.

One tester is good, two is optimal

To ensure optimal and bug-free operation, one tester is not enough! At a minimum, there should be two of you to make sure that no bugs have escaped your notice. It is a question here of preventing potential ergonomic problems, of detecting other imperfections, of having another point of view. Preferably, the developer should test the product, but also the project manager. Their complementary visions allow for a broad spectrum of testing. Of course, if you can be a little more testers, that won't do you any disservice. The implementation of one or more QA testers may be necessary for the development of complex products. These come to test each feature once it is declared as “finished” by the developers. These tests are carried out on the "staging" environment in parallel with the developments. Changes over time are thus much less painful.

Technical performance book, an essential tool

When launching your project, you first had to establish your specifications. This document will accompany you throughout your functional recipe. It allows you to script all the functional and technical actions that you will find on your site. By relying on your specifications, you can then make your recipe specifications.

Technical performance book allows you to move forward step by step and control each feature and route without risk of forgetting due to the density of the elements.

If you do not know how to make a recipe book, at the agency Le Backyard, we can made for you!

Centralize remarks

During your acceptance phase, use a tool to group and organize your remarks. Many items to correct may be detected, it is important to bring them together through the use of a recipe tool. The latter has the advantage of keeping the history of requests, tracking their resolution and prioritizing them, which is essential to stay organized during the test.

If bugs are not properly described, noted, and tracked, they can get lost and adversely affect the user experience. Tools are available to organize your feedback so that it can be easily found, analyzed and corrected. This will make your tests as efficient and effective as possible. Some players use Google Sheet, or ticketing tools like Jira, Redmine.

At The Backyard agency we use Trello. We advise you to use this tool, the free version is more than sufficient and allows you to organize your tickets in a table accessible to all, with an error correction follow-up. At the Backyard, we offer you an adapted offer to help you launch your digital project. From the creation phase, through the specifications to the launch of your product, we are there to monitor and control your project. Once all this planning is done, you can get started with a lot more confidence in releasing your project.

If you need further assistance along the way, please do not hesitate to contact us.

You may be interesed by