Hi, I could successfully create automated Tests for my dummy C Project using Parasoft. But on executing these tests, I get message in console: Collecting tests to be executed... Skipping test suite(s) - invalid CPPTEST_TEST_SUITE_INCLUDED_TO value detected: /Addition/tests/autogenerated/TestSuite_add_c.c ...done. Preparing…
Hi We run parasoft cppclitest in our CI flows as "best effort". In some cases, when there is no available license, cpptestcli sleeps for 600 seconds and then tries again. This will try several times in a loop until end of retries or available license found. In some cases this adds lots of time to our CI flow and users…
I want to include a list of suppressions in the report. When i am running c/c++ from eclipse and enable the 'Supressions Details' option the report contains a list of suppressions. But when i run the analysis from cli with -property report.suppressed_msgs=true the report does not contains the list of suppressions.
We have a CMake buildable project (C source) which we have just imported into Eclipse. The project builds successfully in Eclipse. When trying to run the MISRA 2012 checks via the Eclipse IDE C/C++Test plugin, it reports many files and source lines are available under 'Scope' but under 'Static' it says Files Checked: C/C++…
I am trying to run unit test by executing "Run IAR EW Tests" but I am getting this error Your current license is not sufficient to use non standard test execution flow Build and run tests on IAR C-SPY Simulator (license required) My current license indicates that "Runtime Error Detection", "Static analysis", "Unit test",…
Hi We are running cpptestcli to scan our code inside a docker container. Since we start with clean workspace every time, the scan takes too much time. To try to resolve it, we copied ".cpptest" folder to a shared location, then, on the next run, downloaded it to the workspace. the problem is that we still see long scans…
Tool: Parasoft C/C++test Standard 2022.2 Per the documentation below for cpptesttrace, if the option --cpptesttraceRun-OrigCmd is set to "no", then the original command line will not be executed. However, this option is not recognized by the tool (verified via cpptesttrace --cpptesttraceHelp). Was support for this feature…
Using the Parasoft plugin for Eclipse, I am able to run Parasoft test configurations successfully. Trying to run the same test configuration using cpptestcli results in a error message and a stack trace in the error log. The Parasoft version is C++test Professional 2020.2.0 (10.5.0.20201022B1126). The error output is…
When we analyze our code from Eclipse we use the compile_commands.json file as input. Then we click on the project name and start the analyzation. When we use cpptestcli on terminal the build_commands.json file is also used as input. We set the -workspace argument and the ruleset which should be used. The result is…
If you met some console like above while Generating a executable. Do worry, try this solution. Check your project properties configuration, and check the linker configration. Then check the path of .o file, maybe your miss a ". the code maybe like this:${cpptest:original_options} C:/code/startip.o" Add the missing ", try…
It looks like you're new here. Sign in or register to get started.