Best Of
Re: How can I retrieve/use the project location in a relative path to open and read/write to a text file
You can modify the method to accept two arguments:
def writeString(input, context)
From the 2nd parameter to the method (called "context" in my example), you can call
context.getAbsolutePathFile("File.txt")
This will return a java.io.File object, whose path is created by resolving the path passed into getAbsolutePathFile with the path to the .tst file that the script lives inside. So if the .tst is at c:/myworkspace/myproject/mytest.tst, then the call above would return a File object for c:/myworkspace/myproject/File.txt.
You can view JavaDocs for this method by going to Help > Help Contents > Parasoft SOAtest Extensibility API and viewing the ScriptingContext interface.
jakubiak
Re: I wanted to test an App using SOAtest. How to invoke that app using SOAtest?
Are you testing a mobile app or a desktop app? SOAtest supports web applications, and it can execute Appium scripts against a mobile app - but it does not support desktop applications. SOAtest's sweet spot is testing the APIs that all of those apps make to the backend.
jakubiak
Re: Rules on File Server are changed to invalid
Hi @elch,
I think we identified the issue. It most likely happend when both C/C++test and dotTEST looked for custom test configurations in the same custom folder.
In order to avoid the issue, until we have the issue resolved, please, use different custom folders for C/C++test and dotTEST test configurations.
Re: dotTest 10.3 - Is it possible to edit a rule.
I'm sorry, I don't know why it does not work. It should. Could you please contact our support for more detailed investigation?
Re: cpptesttrace
Hi @elch,
Regarding:
- Create bdf for all project.
- Run cpptestcli on all bdf files for all projects in worksapce in one line command.
There are multiple ways to organize scaning builds into BDF files, and then running analysis on them.
Assuming you want to run analysis on all projects at once:
If you need to create a single BDF for multiple projects, you just need to prefix the build command with cpptesttrace and maybe add a few extra options.
If your build consists of multiple commands, just prefix each of them with cpptesttrace.
In fact, if you specify the same exact BDF to each cpptesttrace command, subsequent builds will be appended to the BDF.
For example:
If you have projects and their make files located at:
$HOME/dev/proj1/Makefile $HOME/dev/proj2/Makefile ...
you can run cpptesttrace as follows:
cd $HOME/dev/proj1/ cpptesttrace --cpptesttraceOutputFile=$HOME/dev/common.bdf make clean all cd $HOME/dev/proj2/ cpptesttrace --cpptesttraceOutputFile=$HOME/dev/common.bdf make clean all ...
Note, that I used absolute path to the BDF file. This ensures that the same exact BDF is used for each build, even if make changes working folders internally.
Once you have the BDF, you can run analysis on all the sources from all projects at once using the single BDF.
If your build command is typically ./build.sh -b, then yes, to scan the whole build you would use:
cpptesttrace ./build.sh -b
perhaps with some extra --cpptesttrace* options, as needed.
Alternative approach could be to create separate BDFs for each project, and then create separate C/C++test projects that can be imported into C/C++test workspace, Depending on your build organization this may be done manually or with some scripting to automate the whole proces. As a benefit, you can then run analysis on each project separately with cpptestcli -resource option, or on all projects at once when you just specify workspace without pointing out to specific resources/projects.
but again, this requires a bit more work, so if you just want to run analysis on multiple BDF's at once, it might be simpler to just "cat" them together, for example:
``cat //cpptest.bdf > main.bdf
Re: Is it possible to edit rule in dotTest ?
Hi @elch,
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.
Janusz
Re: Is it possible to edit rule in dotTest ?
Hi @elch,
Is it updating the rule files ? or just configuration file ?
Test Configuration Editor - which is accessible by right-clicking a test configuration and choosing Edit - edits configuration files.
However there is Rule Map editor - which is accessible by pressing [Edit Rule Map] button at "Configuration" dialog in IDE - using it you can upload/download rule files (which are editable by Rule Wizard)
Janusz
Re: Rules on File Server are changed to invalid
Hi @elch,
Would you be able to tell more about tthe usage scenario?
By "File Server" do you mean just a regular shared network drive where custom rules and/or rule configurations are stored, or Parasoft Team Server (part of DTP)?
Also, what is the contents of rulename.properties?
Re: Is there a way to "push" settigns
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.