Why does my Test Definitions status remain "Not Scheduled" even when I have scheduled the Executions?

0 Likes

Problem:

Why does my Test Definitions status remain "Not Scheduled" even when I have scheduled the Executions?

Resolution:

When you create manual tests they have a status of "Not Scheduled". If you then create an execution, assign the newly created test definitions and the is execution scheduled for a run, the test definitions will still have the same status of "Not Scheduled".

A Test Definitions status is the aggregated result of the statuses of all assigned Execution Definitions, where the version and build are the same.
For Example: A Test Definition has 2 assigned Execution Definitions which have been configured with the same build and version number. Each was executed, one of which passed and one which exited with a status of "Not Executed". The Test Definitions aggregated results is "Not Executed" as one of the Execution Definitions current status for the last execution against that version and build of a product is "Not Executed".

A status of "Not Scheduled" means, that a Test Definition has never been executed. If a schedule is defined and an execution is planned for the future, this does not have an impact. After the first execution has finished, the status is set accordingly.

Therefore only completed executions have an effect on the status of the Test Definition. RFE #39281 has been logged to change the status of a Test Definition to "Not Executed" once its assigned Execution Definition is scheduled to run.


Old KB# 25087
Comment List
Anonymous
Related Discussions
Recommended