As you read in the first part of our blog on the Quality Assurance process at Transoft Solutions, the new features in software such as AutoTURN™ comes from real world engineers through the Product Management team. The next step is testing the software which falls to Carlo Pechuanco, Development Services Manager at Transoft Solutions Inc.
“We try to start testing as early as possible,” says Carlo. “We’ve been testing since development started on AutoTURN 9 in November with all the new features. As soon as the developers started writing code, we started testing. We always want to do testing in parallel with development. This allows us to do two things: First, we verify that we’re on the right track as far as requirements go and what Product Management wants out of a feature and two, to ensure that the code is actually producing correct results.”
Carlo continues, “This results in a very high number of issues in the beginning. The Product Management guys tell us what they want the feature to do, the developers come up with a solution and then the testers test their solution against the PM requirements. This process repeats through several iterations for every single feature until all sides are happy.”
In the past year, a new aspect of code development has been introduced to improve the future state of the products. To use a 1980s reference, it’s like going back to the future. Carlo’s group fixes code so future versions of the software will be that much better.
As he explains, “We are testing each new feature and its interaction with older features. The older features get tested throughout the course of development to make sure they are not breaking along the way. As we write new code, it can be shared with old code. Sometimes new features uncover deficiencies in older features so those things get cleaned up.”
The new version of AutoTURN® incorporates a blend of tried and true functionality with the new innovations from the Product Management group. With each new update, the software captures more of what engineers are looking for. Users will notice improvements that produce results the user can trust.
“Path Control is a good example,” says Carlo. “Path Control has been a part of AutoTURN since I started. In the latest version, we’ve totally revamped it and put a lot of effort into it. With that effort, we’ve made the tool more usable. In doing that, it revealed a lot of problems in Generating Arc Path and all of our simulation code. In the course of developing this improved path control, we had to re-develop a lot of our simulation code and make it more robust to handle more situations that didn’t need to be considered before.”