When we send out a product we want it to be as ‘bug free’ as possible. To that end, we employ an avid testing process, wherein testing starts at the beginning of development and continues even after the product has been deployed.
Our tech team begins the testing process by gaining a good understanding of what the product is and how it should function. After getting a thorough handle on the product, we write a test that, when run, will make sure the product is functioning correctly. We run this test after the product is finished being coded, going back and fixing coding problems until the test is passed. These tests are retained for the life of the product, and are constantly running to make sure that no future additions or alterations damage the product.
After the product passes this initial test, the developers test it further, and then upload it to a test environment (test environments are often clones of live website, wherein testers can demo functionality of new products without affecting the live website). Our quality assurance testers (QAs) manually try the functionality of the new product in the test environment, making sure it does what it is designed to do, and nothing that it isn’t. Strangely enough, the most valuable QAs are those who are agile enough to find ways to ‘break’ the product. The more ways in which testers can try to ‘break’ a product, the more durable and ‘bug free’ the product can become. All of the bugs and missing functionality found by the QAs are sent back to the developers for repair. After a bug is fixed, it must again go through testing.
Before the QAs get into the detailed stages of testing, they explore the product to make sure all obvious bugs and functionality has been dealt with. Then they send out the product to testers throughout the company, as each Internet Truckstop department has a few people designated to help test, with testers rotating quarterly. Each company tester spends an hour a day doing nothing but testing products for functionality and bugs. The more eyes exploring a product, the better, as the diversity of approaches and perspectives makes for a more thoroughly tested product. When company testers find the product to be ‘bug free’ and user friendly, they communicate to QAs that the product has ‘passed.’
QAs continue to test even while they wait for the product to pass through the company testers. After confirming that all bugs have been fixed, that functionality is working and user friendly, and that company testers have given the ‘thumbs up,’ the product is finished, and ready for rollout.
After passing through our developers, our QAs, and our company testers, the product then moves on to its most important test of all – your daily use! Our entire testing process is designed to make our products function in the useful, user friendly ways that you would like it to. We greatly value your feedback because your opinion is the most important of all.
About the Author
Chelsea Baguley, is a certified Scrum Master at Internet Truckstop and works hand in hand with the development department. Chelsea started as a tester at Internet Truckstop and has a keen insight of the functions on the load board.