Environment: Windows XP Workbench 2.6.1 VxWorks 6.3 C++test7.1WindRiverExtension 7.1.2.30 When trying to build unit test cases for execution on a vxworks target the test configuration fails. We are unable to run unit tests on the target. Jeff Estes was on site 1/30/08 and has the details.
LicenseIs there anyway to get a floating license for the command line interface and bug detective applications?
(Entered for David Mann) This topic has been discussed and you have provided a temporary workaround. I have been able to add the missing function definitions inside the auto_incomplete file and been able to get the test generated. I am keeping this issue open until we have a solution for this problem. Please keep me…
(Entered for David Mann) Parasoft seems to generate alot files inside the .cppTest directory. How does this stuff relate to the test suite and stubs that are generated? If we do not configure these files to we incur a compile time penalty, a code overwrite penalty? Please explain.
(Entered for David Mann) This topic comes from our last meeting where we discussed how I can take a unit test driver that I made and compile it on the Green Hill Multi. What I currently do on my actual project is make a unit test driver. It tests all the functionality within my project, include test stubs from other…
(Entered for David Mann) Ok. Here is what I want to do. There will be at time where I would like to use the full functionality of my current project and possibly one or more other projects. For example. I may want to generate the Main project and use the actual code from the Common project. Currently, stubs are created for…
(Entered for David Mann) I am trying to isolate a particular class from the rest of the project. For example, I would like to test only TestExecThread.cpp. But I want to keep the function level testing around. So I am trying to devise a way to not to mix them up. The following picture shows my attempt at doing this (see…
(Entered for David Mann) Is there a way when executing a run unit test to have the report default to a differerent directory than C:\Documents and Settings\mannda2\Local Settings\Temp\parasoft\xtest\? What I am thinking is the following: Currently I am developing the following structure for stubs (see attached): I would…
(Entered for David Mann) I added a function inside AdjacentChannels called BlaBla(). I added it to the .h and .cpp. The .cpp portion is just an empty function. I added a call inside the constructor of the ThreadBase class AdjChannel.BlaBla(). I built the code using GenerateUnitTests followed by GenerateStubs followed by…
(Entered for David Mann) I just observed this when preparing the previous issue. When I added the default constructor for AdjacentChannels, I noticed that I now have two auto_incomplete functions auto_incomplete_6b7324ea.cpp which contains the original stubs and auto_incomplete_2f8f39d7.cpp which hold the new constructor…
It looks like you're new here. Sign in or register to get started.