August 23, 2017

Regression Text

Every time we modify code we run the risk of introducing new bugs. When programmers make changes to software to fix errors that have been identified, it can cause functions that were previously working properly to experience new problems.

As a result, every change made during software development necessitates retesting in order to verify that the previous quality baseline is still intact. Regression testing, also known as verification testing, is the process of analyzing software after a change has been made to verify that the quality has not regressed. Regression testing is performed after a software update but also when the software is ported to a new runtime environment, a new compiler is used or when the software is migrated to a new hardware platform. 

Posted by Jeffrey Fortin in Software Quality

August 07, 2017

Steve Barriault

This is Part Two of my training trip to Vietnam. If you didn't read Part 1, it is here. I walked all the way to an important temple dedicated to the Jade Emperor, not unlike what I saw in China at multiple occasions. What was unique, however, was that a statue of the Jade Emperor was provided with tons of food, such a fruits (OK), ramen noodles and even Oreo cookies! Since people prayed there I did not dare take a picture, but I did so in the next room where a giant turtle statue (pictured below) was exhibited. According to legend, this place is where the emperor gave back a magical sword to the turtle that lent it to the Vietnamese people to throw invaders out (this happened in the 15th... Continue reading »

Posted by Steve Barriault in Journal Entry

August 03, 2017

Steve Barriault

One of the most exciting parts of my job is to go somewhere for the first time. And that is not every day I get to go to a brand "new" country to meet clients. So I was pretty much looking forward to visiting Vietnam this time around to deliver training.

Of course, this can sometimes be tricky. Vietnamese is not one of the languages I know, not even a bit (I did learn how to say thank you, but not sure if my pronunciation is any good). More on that later.

The first two days were spent on the training itself. A question came up that I had to answer a few times already: Any guidelines on how many files should be in a unit testing environment? So, here is my rule of thumb: you should have only the number of files necessary to write a single compound test.

Posted by Steve Barriault in Journal Entry