OnRoad Test Management

Welcome to OnRoad Test Management Sign in | Join | Help
in Search

OnRoad Weblog

February 2009 - Posts

  • Juvander Consulting Tools and Support for Quality Center 10

    We have now done first round of testing with Quality Center 10 and right now the situation looks that OffRoad and TFS Bug Item Synchronizer are ready and can be used together with Quality Center 10 without any issues.

    Other tools still need more investigations and we already know that there are some issues that need to be taken care of. Import Export Utility is the next one to be taken under work.

  • BETA: TFS Bug Item Synchronizer version 2.0 for Quality Center

    Next version of TFS Bug Item Synchronizer version 2.0 for Quality Center is get closer.

    Today we have put first version out where are two major changes compared to version 1.6:

    • Possibility to define master for each field. Both Quality Center and TFS or None can be marked as master for fields. If None is selected, it equals current behavior.
    • Requirement synchronization between Quality Center and TFS. We have enabled an simple version on these two systems work together.

     image

    About requirement synchronization, this is not perfect yet as TFS has some limitation on it.

    The way it works right now is that you must define one root requirement in Quality Center and all mapped requirements are then created under this node. After requirement has been created from TFS in Quality Center, it is possible to move this requirement into different place and also requirements originating from Quality Center can be in any place.

    Reason why it works now like this is the fact that TFS does not have any hierarchy between requirements in current releases. It is only possible to define related work items without any parent - child -relation.

    There are some custom work item controls that enable this, but not out of the box TFS project can do it.

    Also, on this scenario where requirements are synchronized into one folder, there exists some limitation on Quality Center side: Requirement name must be unique within requirements children. For this we added automatic renaming of requirements, duplicate requirement names are added text '_Copy_X' at the end, where X is the number of duplicate requirement names.

    But let's see how the feedback on the current version is going to be and after that decide which way to go with this.

    This version can be found on our BETA downloads (requires registration to the site).