Best Of
Re: How to execute unix shell scripts from within SOAtest
You are using the SFTP Client from the Parasoft Marketplace, right? I haven't tried but maybe it can execute arbitrary remote commands on the remove host, like call "/bin/bash" with a path to a script as an argument. I haven't tried this but thought I'd mention this first just in case it happens to work.
Alternatively, there are arguments that you can pass to the unix "ssh" command to execute a command on a remote host. So, if you are running SOAtest on Linux or Mac then you can configure an External Tool to invoke "/usr/bin/ssh" directly. If you are on Windows, you could use "ssh" from Cygwin or maybe call something else like winscp or putty which has a similar command line feature.
Re: Misra rule violation shows up when not running static test on full project
The static analysis rules (except GLOBAL and BD rules that can be cloned to MISRA2012 ) analyze every translation unit (source file and its headers) separately. Rules 'MISRA2012-RULE-20_9_a' and 'MISRA2012-RULE-20_9_b' should report the same number of violations in a file in the output scope independently from testing scope. If new violations appear when you narrowing the scope, then please check what is the limit of violations per rule. Maybe, when the whole project is tested, then the limit of violations was achieved for these rules and some violations were not reported. At this moment I don't have any other explanation for this behaviour.
mstaron
Re: Intro to Virtualize?
Its likely that it was a blog post rather than an article. Take a look at the following link to view all of @Chris Colosimo blog posts: https://blog.parasoft.com/author/chris-colosimo
You can also find some how-to videos in the following link to help you get started:
https://www.parasoft.com/support/service-virtualization-and-api-testing-how-to-videos/
OmarR
Re: Intro to Virtualize?
Aside from videos, I think Chris often publishes stuff here as well:
https://blog.parasoft.com/topic/service-virtualization
Re: Test case generation
Hi @raj,
We can try to solve this specific problem, by adding the following line to c.psrc and cpp.psrc files of your custom compiler.
edg.enter_type name=__builtin_quad type=int
And then see if tests were correctly generated.
But since this is not supported combination, I recommend going via the support team as there may some other modifications required.
Mirek
Re: Test case generation
@raj - can you please create support ticket so we can better track it? Thanks!
