Over the past several years, build management and Continuous Integration tool vendors have suggested that these tools should manage not just authoritative builds from source control, but also replace the test builds done on the developer’s desktop. While useful technology in specialized situations, these preflight (precommit) builds have the potential to undermine best practices -- doing more harm than good.

Read more...

As AnthillPro 3.6 nears release, we want to give readers of this blog a sneak peak into some of the new features. In this first look at 3.6, we want to look at the new metrics around the test history. Test history metrics work for any kind of testing tools that AnthillPro interacts with.

Test history reports will help teams visualize changes in the rate of successful tests and the number of tests for a given project.



Since AnthillPro understands the test data well, it can identify which tests and test suites have been the most problematic over the time period and which tests take the most time.



As you can see, in this particular example, most of the tests seem to run in under a second, but several tests take noticeable amounts of time. This might indicate that better mocking would be helpful here to address the handful of slow tests.

There are a few more refinements we will be adding to this feature over the coming days, but we're excited to add this kind of trending. Similar functionality is being added for other types of information as well.