Test Design Studio 2.0 Beta 3 is Now Available!
You can use the following page details of the new features:
Test Design Studio 2.0 Beta Page
You can also use the our
RSS Feed to follow updates on the beta.
Finally, visit the
Beta Downloads Page to get the software.
QC 10 Resources Version Control
Version Control is now supported for the Resources module of QC 10. The API for versions is totally different than the one used for tests (thanks HP), so please let us know if you encounter any issues with versioning.
XML Suppression of Warnings and Errors
This release addresses all known parsing issues, so please let us know if you encounter any false error reports. Also in this release is the ability to suppress errors/warning in code. This is done by using XML comments and the 'suppressmessage' tag. The following example shows how two messages can be suppressed for a particular function:
''' <suppressmessage checkid="CA0101" />
''' <suppressmessage checkid="CA0104" messageid="myUnusedParameter" />
Public Function MyFunction(ByVal myUnusedParameter)
' No Return Value
End Function
You will see the Check ID listed with the description of each error in the error list. You can also use the XML IntelliSense to auto-generate the suppression message for you (available when typing a new XML comment after warnings/errors are displayed for the item). You'll notice that the unused parameter rule has a second attribute called "messageid". That is used when the same rule could apply to more than one item (i.e. more than one parameter). The "messageid" will correspond to the entry being suppressed.
The XML suppression messages are recognized at the "container" level... that means functions, subs, properties, classes, and script-level comments. The message being suppressed should be placed on the closest container. So if you have a public instance of a variable in a class, you would suppress that message by placing XML comments on the class, not on the variable itself.
Plug-in Rules
This build of TDS also implements support for plug-in rules. Customers who would like to have their own custom rules applied within TDS can contact us for support. These rules could perform analysis such as enforcing naming conventions or code techniques.