Rally is the centralized repository for our… everything. We use it for our Story Cards, Defects, Test Cases… everything. Our test execution platform doesn’t require it, but their simple API makes things extremely easy to access via script. It doesn’t do real Configuration Management - it doesn’t build the software or perform source control. It just helps us manage the process and all of the test data we generate.
In the last post, I showed a basic code snippet and described a little about how we implement our test scripts for automation. This post will go more into detail about how the underlying objects are implemented.
It’s been a long time since we did regular updates, and that’s about to change. We’ve spent the past 18 months building and solidifying a team structure and a test platform, and it’s now time to start talking about it. We intend to release some of our work under the GNU public license, and this background information should help you in making the decision to use it.
We will post a series of articles, which will describe our processes in detail. Then we’ll round it out with several examples of how this framework solved most of the problems that typically plague test automation efforts. Comments and suggestions are welcome.
(more…)
