Search This Blog

Friday, July 20, 2012

Release of XStudio 1.6sp4

XStudio maintenance release 1.6sp4 has been delivered.
Here is the change log:
   * Ability to create and link bugs from manual launchers when interfaced with
     JIRA, Mantis, Bugzilla, TRAC, Generic connectors
   * Include the name of the schedule in the session's name
   * Defect report: include 'Found in' and 'Fixed in' (SUTs)
   * Keep as much as possible the former order of the tests in a campaign when:
     - adding/removing some tests from this campaign
     - copying this campaign (and adding/removing tests on the fly)
   * All dialogs are now NOT modal and NOT on top anymore except for MOVE/DELETE
   * Manual launchers's dialog NOT on top anymore
   * Bug-fixes:
     - Schedule's SUT not identifiable
     - Impossible to submit a commment on not executed manual tests
     - Performance issues with Free, Pro and Business licenses
     - Now able to use "All combinations", "Pairwise", and "Import Dataset from
       CSV" feature even with a single parameter
     - Wrong header order in the specification report
     - When creating/linking some bugs from the Tabular_manual launcher they
       do not appear in the list on the test cell   
     - Exception when retrieving tests and testcases including special characters
       in their name because of the parametrization (pairwise algo/dataset)
     - Tabular manual launcher: display DISTINCT bugs in the test cell
     - Create generic bug on the fly fails
     - Oracle db: exception while affecting a bug to session's tests
     - Localization typos 
     - Couldn't delete a bug of type "generic"
     - Duplicate custom field values (from SUT/test cases) sent to the launcher
     - Generated tests from requirements/specs cannot be executed
     - Third-party requirement or bug-tracking system should not appear while
       editing a team's access rights 

Sunday, July 8, 2012

XStudio 1.7: Automatic generation of residual tests campaigns

Let's imagine you have 4 different test campaigns that have been possibly executed by different people.
These 4 campaigns may have tests in common (maybe all of them, maybe none...)
They have been executed possibly several times each.

Now, I'd like to create a new campaign containing only a selection of the failing tests from these 4. This could be tests that failed once in the iterations or only those that have failed in the last iteration etc.

This manual task may be pretty tough and boring.

But it's easy enough with XStudio 1.7's automatic generation of residual tests campaigns.

Step1: Select all the source sessions



Step2: Choose a destination folder and define the rules that will be used to generate the residual campaign



Step3: It's done!


  

Tuesday, July 3, 2012

Release of XStudio 1.6sp3

XStudio maintenance release 1.6sp3 has been delivered.
It fixes a couple of minor issues (mostly only when used with an Oracle database):

   * Additional protection while printing the custom fields (in the launchers)
   * Additional protection on changes information length <= 255 chars
   * Bug-fixes:
     - Localization of certain terms not found in not-English languages
     - Files in the doc tree are never detected as locked (Oracle only)
     - Improved Spanish localization
     - Some large text fields does not support > 4000 characters (Oracle only)
       * defect: defect_description, step_to_reproduce, fix_description
       * test: test_description, test_prerequisites, additional_info
       * test case: testcase_steps, testcase_description, additional_info
       * requirement: requirement_description
       * specification: specification_description
     - Couldn't change the value of the defect custom fields (Oracle only)
     - Do not escape CLOBS when inserting them (Oracle only)
     - Workaround to avoid having a " " canonical path