Embedded Software: Automating Tests From Hand-written Requirements

Abstract

As the complexity of systems and software increase, the need to determine specific test cases for the requirements as well determining a complete test suite become more complex and time consuming. Additionally, testing typically comes at the end of the process, increasing cost and schedule pressures in an effort to get to market. This paper will introduce a technique, process and toolset that can assist in making reducing the cost and schedule pressures of testing a system. According to an article written by Ricardo Queiroz, “One of the big questions tormenting all managers since the start of any project is: "when should we start testing?" (Another usual big question is "why should we care?" - because of the money involved, obviously) the question seems hard, if you do not find serious arguments to select the starting date. Let me help you. So, when should you start testing after months of hard work developing the product? The answer is simple: the test team should be involved from the beginning right to the end! And this recommendation is based on many factors: testing saves time, effort and (you guessed it!) - Money!"