Software testing systems

[shadow_man]

Hi,

I've made a setup guide for Klaros TestManagent if anyone is interested:

http://jerome.co.za/klaros-testmanagement-software-an-installation-guide-ubuntu-12-04-lts/

Additionally i'd like to know what others are using for their software tests - whether it be test software like Klaros or bug trackers like bugzilla, mantis, bug genie etc as i'm looking for things to implement to make life easier.

Thanks,
J

 

[zippy]

Companies I worked for wrote their own test data management systems. The most complex was a system which allowed for test environments to have code builds deployed to test environments and also for separate test data builds to be deployed on top of those. Web based front end.

Each test data build was basically SQL scripts which loaded pre-defined test cases. At any time the systems where supporting numerous test environments each with its own database and own application server workspace. All unix based. The system allowed for the deployments to be scheduled overnight to minimise downtime in working hours.

The system also integrated with the IBM Rational test system to automatically run regression tests as part of the overnight code and test data deployment.

The servers where all based in Chicago and Washington DC, while UAT testers where based in Mumbai and Bejing. On site testing was done in Newcastle, Manchester and London, so you can imagine the scale of managing all this.

 

[cguy]

Everywhere I've worked it has been home built. The front end is usually a combination of a web frontend and a separate app (C#) that can be used to review the test data in detail, and compare or graph the results along some dimension. The backend is usually a collection of scripts (current place uses Python), that distributes the tests over many machines, and sets up isolated environments for automated performance testing.

Builds and tests are run automatically on code check-in. More detailed testing is run over night (with binary regression searches for failures seen in order to isolate the exact change list). Changes can also be manually submitted pre-checkin for verification purposes. The whole system is integrated into a custom bug tracking system.