Mirek ✭✭

About

Username
Mirek
Joined
Visits
170
Last Active
Roles
Members, Staff
Points
70
Badges
9
Posts
78

Comments

  • Hi @elch, Compiler should not matter here. If the psrc option was specified correctly you should see "Executing command:" tag in the output somewhere before the error message. Below you can see an example from my environment, we are looking for…
  • Ok, me previous post was not complete because I've put parameter to -psrc option in ang. brackets which were interpreted as a tag and rendered out. Your command line needs to look like below: make CPP="cpptestcc -compiler gcc_3_4 -line-coverage -…
  • Hi @elch, Please create a simple option-file with any name, like "opt.psrc" and add one line to it: pscom.logger info.pscom.os,TRACE Then modify the command line used for instrumentation: make CPP="cpptestcc -compiler gcc_3_4 -line-cover…
  • Hi @raj, Unfortunately, it seems there is no quick/easy workaround for this problem. C/C++test parser does not support this construct (extern "asm"). I will discuss this with the team and see if there are any non-standard hacks available.
  • Hi @elch, This may be because your make file compilation rule automatically includes the instrumented files into original build. Please check inside your project for all directories named ".cpptest" and remove them. Then invoke the build comma…
  • Hi @elch, Can you please provide the command line + exact error message from the console?
  • Hi @elch , If you want to collect coverage metrics you need to switch the build to coverage mode and instrument the EXE. At any time you can disable the coverage mode and rebuild your EXE to have a clean build without any coverage instrumentat…
  • Hi @elch, Can you please elaborate command line invocation for generating report. This is just a single invocation of "cpptestcli" command with a small set of options to generate the coverage reports and send coverage data …
  • Hi @elch, I'm not 100% sure I understand what do you mean by EXE file, but I general I'm inclined to say yes. If you apply our "lightweight" coverage from C/C++test standard, you should be able to instrument your project in VS in a "transparent" …
  • Hi @elch, C++test standard offers a lightweight coverage integration for VisualStudio. You can add a special MSBuild extension (which is done per project) and from this moment you will have an option to build a specific project with coverage. Bui…
  • 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 …
  • Hi @elch, Are you using C++test based unit tests? or something else like GoogleTests? or CppUTest? If you are working with GoogleTest or other open source UT frameworks it is recommended to use C++test Standard edition, which includes a lightw…
  • Hi @raj, So now we are facing a problem with unsupported compiler. C++test does not understand the language extension that is supported by your compiler (__builtin_quad). What is the exact name and version of your compiler?
  • Hi @raj, Ok, I see now what is going on. Please go to custom compiler directory, open gui.properties file and locate the following two entries: analysis.generation=false analysis.execution=false Change those to: analysis.generation=true…
  • Hi @raj, There is not enough information in the console, you need to increase console verbosity (Parasoft menu-> preferences-> console : set to high) and clear cache (project properties->Parasoft->C++test->Other settings->clear)…
  • Hi @elch, Yes, "Unit Testing" and "Coverage" license features are required if you want to deploy unit testing practice.
  • Hi @elch What are the advantages of running unit testing with C++ with C-spy ? This way we can achieve full automation, IAR debugger interface handle all actions required to download the test executable, start execution and…
  • Hi @elch, In general yes, all the testing actions are done from eclipse however, we use the IAR C-spy interface for running unit tests on target or simulator. So once the test executable is ready C/C++test calls C-spy, via the script generated b…
  • Hi @Benjamin If I understand your case correctly you should be using the following syntax: *param = [some int]; For example: *param = 22; Let me know if it helps.
  • @Andrey Madan However, when we want to launch the executable outside of C/C++test by navigating to out scratchpad folder and executing cpptest//unit_data/current_blah/testProject.exe from the command line - we get the SAME error as displa…
  • Hi William, Can you please provide the full console log? Please clear the cache before (Project Properties->Parasoft->C/C++test->Other Settings->C/C++test temporary files>Clear?) and make sure console verbosity is set to high (Par…
  • Hi @lintu, I'm not sure if I get it right, please confirm that my understanding of the problem is correct: you have a test case: void TestSuite_copy0716_c_ac302433_TestCase1() { parameter [0u] = CPPTEST_DS_GET_INTEGER("[IN].CurrBuff_0"); …
  • Hi @prince , For automatic test cases generation C/C++test analyzes: * function signature, specifically the types of parameters and return value. For every parameter, based on the type of the parameter it is trying to generate set of corner …
  • @prince Is there any chance that some source files were modified between both runs? Maybe only header files?
  • Hi prince, Based on the output you are getting, it seems that your shell cannot find the cpptesttrace executable, you need to do one of two things: * invoke cpptesttrace using full path, for example: [[email protected] src]$/usr/loca…
  • Hi davemr, I'm sorry for not responding sooner - I'm traveling, hence the delay in response. I would not give up on the idea of creating a single test executable. Please note that it is a perfectly valid scenario to call the original symbol …
  • Hi davemr, Auto stubs have lower priority than original definitions, so if you have both in the test scope, the original definition "will win". User stubs, however, have higher priority than original definition, so if you create a user stub fo…
  • It is not a "standard error" message from the tool. I guess there may be some issue in your local configuration files. Please contact our support team - short streaming session will be the most effective way to solve this problem. Thanks
  • iccarm_5_5 is a very old compiler it was deprecated and removed in 10.4.0. Is there any option you can upgrade your project to use a newer version of IAR compiler? You can try using iccarm_6_1 instead, there are good chances it will also work.
  • Could you please post a command you are trying to execute and the exact error message?
  • Yes, this is the recommended approach. If you are using Professional, and IAR for ARM you can try using importer, please see "Importing Projects with IAR Embedded Workbench Support" in the user manual. But bdf is a recommended approach
  • Hi @elch, There are a few options here, you need to start with generating the bdf file from you IAR workspace, you can do it, for example, using the following command line: cpptesttrace --cpptesttraceProjectName= --cpptesttraceResponseFileOpti…
  • Hi, Is there support for cpptestcli command line for IAR? Can you please add more details? What do you mean by support for IAR projects? If you mean analyzing the project using "-input ? Also, which version of C++test are you using?
  • If function B lives in the same static library (SL) as function A, then at this moment it is not possible to stub out the call A->B. Stubs are applied through the source code instrumentation, and in case of a library, we are dealing with the bina…
  • What you could do is to have separate instrumentation settings for "test files" and "additional" files. You can select instr. settings for those two categories of files in the test configuration->Execution->General->Instrumentation mode->…
  • Helper question: What kind of testing is done on your project? Unit Testing or Application Coverage Monitoring (system level tests).
  • From your description, it is not clear where the problem is. Perhaps it would help if you could describe what are you trying to achieve.
  • it fails to find any non-static symbols (functions). When you use "Collect Stub Information" Built-In test configuration on a project, Stubs View will be populated with symbols/methods that are called from the project's source, not th…
  • "Instrument Selected Source File(s)" check box enables/disables all instrumentation features for selected file. When the check box is unchecked, C++test will not instrument specific file at all, it means no coverage, no stubs, no stack trace reporti…