Search This Blog

Wednesday, April 4, 2012

Release of XStudio 1.6a6

This has been released yesterday.
It includes many bug fixes as well as the major new feature that add to your SUT and campaign tree a "Quality" column indicating an index of quality of the SUT.

Details of the 1.6a6 add'ins:

   * Quality metrics on the SUT tree
   * Quality metrics on the campaign tree
   * New unified colors for progress bars
   * New areas selector on the left-hand side
   * Agent not responding timeout set to 30 seconds
   * Bug-fixes:
     - Incorrect UI indicators when a session is queued too long on
       an agent
     - Session not starting when queued more than 15 minutes on a remote
       agent busy with some other sessions
     - Refresh the progress at the end of a session execution
     - Too many stats recorded: XStudio frozen when selecting the integrated
       bug-tracking root node
     - Wrong color returned for the graph in the iPhone/iPad app.
     - Incorrect statistics reported in email notifications when re-executing
       a manual session
     - Exception while selecting some folder in the Campaign's content tab in
       the upper test tree
     - Main tree refresh issues (ordering) if defect tree is not in the user
       profile
     - Exception and inconsistent behaviour when modifying sprints and backlogs
       (due to velocity chart refresh)
     - Incorrect Bamboo report generated in case of test failure with messages
       (typo in the CDATA opening tag)
     - No more timeout on the sessions that have been queued for a long time.
       The 30s timeout for "not responding agents" now applies only starting
       from the point where the session has really been started by (at least)
       one agent.
     - Wrong background in the campaign tree in some cells
     - Force the stop even when a session did not really started (in ARMED
       state)
     - setCampaignSessionAgentStatus() called only the first time
     - Error while trying t get the ascending/descending icons
     - "generate spec" vs "generate test" button depending on if the
       specifications are enabled in the PLC
     - Coverage label different in the form depending on if the specifications
       are enabled in the PLC
     - Generate specifications does not update coverage on the requirement if
       necessary
     - Generate tests does not update coverage on the requirement if necessary
     - Same width on progress bars in the same tree
     - Wrong new SQL query to retrieve latest results (for quality)
 
Enjoy!

1 comment: