Plastic SCM GUI testing

Thursday, May 10, 2007 , 0 Comments

Last week I wrote about the three basic layers of testing we run here at Codice to check Plastic SCM functionality release after release.
Each weekly release (or almost weekly depending on the specific workload) passes through long hours of automated GUI testing. As I mentioned we are currently using AutomatedQA TestComplete which is a pretty good tool specially considering the price/quality relationship.
We also run the GUI tests each time a task is finished (and its associated branch is closed), so at the end much testing hours are run.
The following screencast is just a short fragment of a test run, and shows the Plastic GUI under heavy user testing.

Nowadays several tools are available to run those kind of tests on Windows based systems, but there is a huge lack of tools for the Linux world. The good thing with TestComplete is that it is good enough (and getting better release after release, indeed our team is busy today migrating to the last 5 release, and it seems distributed testing runs better now).
The one I know for the Linux world is:, but I never had the chance to try it.
There are other options like, or

Happy testing!

We develop Plastic SCM, a version control that excels in branching and merging, can deal with huge projects and big binary assets natively, and it comes with GUIs and tools to make everything simpler.

If you want to give it a try, download it from here.

We are also the developers of SemanticMerge, and the gmaster Git client.

0 comentarios: