If you are using C/C++test or dotTEST command line engine, the best way is to prepare properties file and pass it to the engine via -settings option.
If you plan to work with the GUI, the best way is to setup GUI on one machine with connection to license server, DTP, other settings, and export them using Parasoft menu> Preferences...> Parasoft or Parasoft menu> Options> Parasoft (depending on the IDE). Once exported, you can then import settings on other machines upon the first GUI launch.
Just to double check, did the issue show up with C/C++test or dotTEST?
created a ticket and solved the issue.
Setting "Multiple Data Source Iteration" to "Flat (lockstep)" solved the issue
Note: This option exist only at the root level default test suite.
Thanks a ton to @Ramiro Martinez
Let us move the discussion to support channel for now. I will contact you by email.
The rules are editable locally on a user computer where Rule Wizard is installed - because Rule Wizard is not a web application, it is a local application.
So the best way to share the newly locally-edited rule - to share with a team - is to use DTP - to publish the rule to a rule map in DTP and have all the team use the same DTP test configuration associated with the rule map.
Summary - about using DTP as a central point to share with team:
1. You have a custom rule(s) (edited by Rule Wizard). You have a DTP server.
2. Create (or maybe you already have) a rule map on DTP.
3. Upload the custom rule(s) files to the rule map (3rd tab in Rule Map editor) in DTP.
4. You have some test configuration(s) which you use. in order your newly-uploaded rule is visible in these test configuration(s), the test configuration(s) need to be associated/linked with the rule map (where the custom rule has been uploaded). The association can be done by editing test configuration, going to "Static Analysis" tab and choosing rule map name from combo at the top of the rules table.
We are not sure we understand what do you mean by saying "child and parent rules"?
And what kind of error about child link do you reference to?
Yes it does. I exported the settings again and was able to get the comments to show up the 2nd time around. I noticed that only comments from the lowest level of the test suite shows up. I only need the comments from the top level if possible because I'll be including a lot of tests and that report will get pretty large and messy if it expands out every single one of my .tst files. Ideally, it would be better if I can generate comments outside of the test suite summary so I can just give a quick summary of what each .tst file is testing.
I will contact you through support channel regarding this.