FIGURE 1: GTEST in Visual Studios IDE
FIGURE 2: Example test suite output of passed and failed tests
|
KEYWORDS: C++, Programming, testing and validation, team work
During my internship at NASA Glenn Research Center, my task was to implement a test suite for the center's Autonomous Power Controller. I wrote the test suite using Google's testing framework(Gtest). The test suite was comprised of unit tests that tested all internal functions and integration tests that tested all the services of the APC in a simulated environment. All the tests had a custom error message that would be displayed when their was any failed tests. By the end of my internship there was more than 350 unit and integration tests. When my test suite executable is ran, it asks the user if they want to run all tests or allows them to put in multiple phrases and any test that contains one of those phrases will be ran(since running all tests takes a long time). The test suite executable also also starts all the services in the background so the user only needs to input which tests are ran. I also to overcome some obstacles to finish the test suite. Some of the APC team would often not update their APC code while working on their sections because some of the team used Windows and some used Linux in different IDE. When ever someone would push their work to the team's repository there would be IDE and OS problems which was a problem for me because I was putting everyone's work together in the team repository for my tests. As I got each members code, I modified it to work for Windows/Linux and Linux/Netbeans. After I added their code, that member just was able to update their work in the repository frequently. |