As you already know, while executing manual testing, the launcher provides instructions to the operator to execute actions (and do verifications). The launcher is also configurable so that some timing restrictions can be added. For instance, it is possible to give 10 minutes maximum for the operator to execute the actions/verifications (i.e. you need to test that a message appears on the screen of the SUT in less than 10 minutes; if the operator doesn't validate that he saw that message within the 10 minutes then the test is automatically set as failed).
There is no more timing configuration to set for the whole campaign session when creating it. However, there is now a much more flexible way to handle timeout for manual tests: by default all the tests belonging to a category associated to manual or simple_manual launchers have no timeout. If you want to set some specific timeouts to a test you just need to associate to this test one or several of the following attributes (with a value for the timeout):
- timeout test description (ms): maximum delay to validate the test description
- timeout test prerequisites (ms): maximum delay to validate the test prerequisites
- timeout testcases execution (ms): maximum delay to execute any actions or verifications implied by the testcases in this test
When manually executed, each test will be applied with their specific timeout values.
Without timeout
With timeout
Note also, that all these attributes are dynamic. This means that when creating the campaign session, you can overwrite any of these default values (on each test if necessary) to customize one campaign session execution:
This new feature will be available in XStudio 1.0a2 that will be delivered around the 13th of September at this location: http://www.xqual.com/support/download.html.
No comments:
Post a Comment