Search This Blog

Saturday, March 17, 2012

XStudio 1.6: New progress metrics

One of the most important question you need to figure out when you're a test manager is "when my test campaigns execution will be completed".

You can get the answer to this question without a single click starting with XStudio 1.6a5.

There are 2 different types of progress metric you can get:
  • Progress in terms of test cases executed versus test cases left
  • Progress in terms of timing: how much time has already been spent but more importantly how much time will be necessar to complete the execution. When you create a test in XStudio you will be asked to give an estimated time for execution. But each time this test is executed, XStudio measures the effective time spent and correct the original estimation. The time necessary to execute a test is calculated from the ten last execution and allows estimating the time necessary to complete the session execution.
The metrics are available directly from the general campaign tree.
When you select "Test cases executed" in the selector at the top of the tree you 'll get the progress in terms of test cases executed:


If you select "Estimated time" in the selector at the top of the tree you 'll get the progress in terms of time spent vs time still needed to complte the session:


The even better news is that If you organize your campaigns in folders that represent something (a functional area, a complete release, a package etc.), the system will consolidate the progress and recursively propagate the metric to parent folders.

This way you know how much time is necessary to finish all the sessions included within a folder for instance.

This feature is available in XStudio Professional, XStudio Business and XStudio Enterprise.
 

3 comments:

  1. I like this feature, it gives a quick view of the status of test execution!

    ReplyDelete
  2. Looks nice,
    I wonder:
    1. How will it look in exported Report (assuming that will be available)?
    Can we limit the presentation level let's say to 2nd level of folders below selected root we execute it on? (Managers need summary and not fully blown details)
    2. Can we override the calculated estimation at any given time?, or block auto calculation for a specific item - for instance we sometimes report the results after executing - so recorded time is much faster then actual time - this might confuse the calculation.
    3. In order to use this - we need to define all campaigns and sessions in advance (this is not always feasible), if we do - we must have the ability to update Tester, Site and SUT right before execution - as these might change.
    We also need the ability to "Close" session - if we do not intend to complete it - so its remaining unexecuted items will not be calculated as remaining time.

    @halperinko Kobi Halperin

    ReplyDelete