RSS Feed

Axe Test Automation Platform

Wondered if anyone else has had this problem when using Axe.  I am not sure if it is an issue between TestPartner and Axe or if it is something that I have done in Axe.

Tim,

This situation can occur when the test results aren't properly updated at the end of a test or run. Usually this is caused by one of two things:
* The script failing to get to the end and not being picked up by error recovery. Possibly due to a syntax error or more serious problem with the execution tool itself (i.e. An Unhandled Exception).
* This can also occur when a custom function uses a call to the Axe API inappropriately, most commonly during a custom validation.
If you are confident that the tests are passing, the it may be worth checking your custom functions to check for any calls to the AxeAPI that might be out of place.

Duncan

These tests are definitely running, and should be passing.  Especially since some of them are dependencies for the next test that has passed!

This behaviour only happened when I split my spreadsheets in two.  I split the sub tests away from the tests and run sheets.

The only time this is a real pain is during debugging as the runs still pass when run.

Fot this particular problem, I suggest emailing support@odin.co.uk with the relevant details and this can be tracked as a support request. If you send on the spreadsheet tables and zip up a sample results folder that contains an example of the problem this will help in diagnosing.

Duncan

Just in case anyone else gets this problem the issue was that my spreadsheet name contained an '&' in it.

We will enhance Axe in the next release to allow use of the ampersand character in workbook filenames.

Sam