March 2008

We continue to perform stability tests on both our MGTS and EVO interfaces. These tests include:

• Utilising the TestAce CTE server at Prosser Telecommunications to perform overnight parallel runs on their 3 EVO’s
• Running parallel overnight MGTS execution (utilising 6 MGTS cards spread over 2 MGTS P400’s) running over 18,000 test cases (which are a mix of standard simulation tests, linked tests and half call tests).

February 2008

We have extended the TestAce CTE MGTS interface to support linked tests and half calls (i.e. syncronising and running both an MGTS receive test script and MGTS send test script).

We have sent a TestAce CTE Server to Prosser Telecommunications in order to finalise our EVO interface acceptance testing. Prosser have kindly allocated 3 EVO’s for this purpose, which we use on a regular basis to test both stability and parallel EVO test execution.

We have now had 2 successful trials of TestAce CTE at a large telecommunications network operator.

January 2008

January was a busy month for us. We have visited test tool companies, service providers and operators in both UK and Europe to demonstrate the power and simplicity of TestAce CTE.

December 2007

After some investigation and market research, we have decided to develop a JUnit V4 interface for the TestAce CTE. This version of JUnit is widely used as well as being backwardly compatible with JUnit3.

Other interfaces will be developed based on market research and customer demand – we openly listen to what people want, so please feel free to drop us a mail to suggest any interfaces that you would like to see in TestAce™ CTE.

November 2007

The TestAce CTE now supports the execution of tests on 3 hardware test tools – Catapult MGTS, Catapult DCT and Prosser EVO. We are running stability tests on these interfaces.

September 2007

We have hit the huge milestone of TestAce CTE development complete this month!

Our development team will now split into 3 TestAce CTE activities – testing, hardware interface development and investigating interfaces into existing software testing frameworks. We are still on track for a mid January 2008 completion date, albeit with a 2-3 week delay due to our desire to perform additional performance testing.