Using Parasoft C++test with Wind River Workbench 4.x / VxWorks 7.x

Transcription

1 Using Parasoft C++test with Wind River Workbench 4.x / VxWorks 7.x Jeff Estes Senior Solutions Architect estes@parasoft.com

2 Table of Contents Getting Started...1 Introduction...1 Requirements...1 Setup...1 C++test Distribution...1 C++test Installation...2 C++test Path...5 C++test License...5 C++test Uninstalling...6 Known Issues...7 Configure WRWB for Usage with C++test...8 WRWB Environment Variables...8 Configure Project Code...8 Initial project directory setup...8 Create C++test / WRWB Project...8 Create a DKM Managed Build project using the ATM example code...8 Configure include paths for project Test Build the Project Configure Project for Using a Build Data File (BDF) Setup and Test Project Command Line Build Run cpptesttrace to Generate the BDF Edit the BDF to Remove cdtd.c Build Information Configure C++test Build Settings C++test Static Analysis (SA) Setup C++test SA test configuration Run SA on ATM Project SubSubtopics C++test Unit Testing (UT) Create a target connection for VxSim Create VxSim Project Modify Kernel Configuration and Build VxWorks Capture VxWorks Location of use in Test Configurations Create test configurations... 19

3 Generate UT one per function configuration Run UT DKM on Simulator (Project Scope) configuration Generate Unit Tests Generate Test Suite and Test Cases for the ATM.cxx class Exclude Unit Tests folder from Project Build Run Unit Tests Summary... 28

4 Getting Started Introduction This document provides information on using Parasoft C++test with Windriver Workbench (WRWB) 4.x / VxWorks 7.x. C++test does not currently officially support WRWB 4, and there are changes in this WRWB release that are not compatible with C++test. However, this document provides workarounds for known issues that will allow installation and usage of C++test capabilities with WRWB 4.x Note: This document does not go into detail about how to use C++test with WRWB. But assumes the reader knows how to use C++test and provides quick examples for running Static Analysis (SA) and Runtime Analysis in this environment. Again, this is not a supported environment, so there are no guarantees that this will work in your environment with your code. Additional information on usage of C++test with WRWB can be found in the C++test Users Guide distributed with the product Help and PDF: <CPPTEST_INSTALL_DIR>\manuals\cpptest_desktop_eclipse_user_guide.pdf This document provides step-by-step instructions on how to perform the following: Obtain C++test - download information Setup the pre-requisite Workbench installation Install the C++test Plugin for Eclipse into Workbench Obtain and install C++test licensing Verify successful installation of C++test Create a sample project and run: o C++test Static Analysis o Generate C++test Unit Tests o Run Unit Tests in the Workbench Simulator and collect results Brief analysis of C++test results to verify setup. Requirements This document was written and verified in the following environment: Microsoft Windows 10 Parasoft C++test (parasoft_cpptest_desktop_10.3.3_win32_x86_64_eclipse.exe) Wind River Workbench installed, licensed, and configured. VxWorks 7.x Simulator The setup should work with similar environments, but it was tested with the above. C++test version must be Desktop Edition or higher. Setup C++test Distribution If you already have the C++test 10.3 Windows 64 bit Eclipse plugin distribution and license, go to the next section. 1. Open a web browser to 2. Select Customer Portal at the very top of the page. 3. Login using your Parasoft Portal credentials or Register for access. 1

5 4. In the left pane, select Products & Licenses 5. In the Downloads section, select: Products: C/C++test Platform: Windows Version: 10.3 Installer: C/C++test Desktop for Windows x64 (Eclipse plugin) 6. Select Download and save the distribution. C++test Installation To install the C++test Eclipse plugin into Wind River Workbench 4.5 on Windows: 1. Run the C++test plugin installation executable that was downloaded above: parasoft_cpptest_desktop_10.3.3_win32_x86_64_eclipse.exe Note: If using Windows 7 you must run the installation executable as Administrator 2. Select Language and OK 3. If a previous version of C++test as installed, you will need to uninstall it before continuing. See below 4. Next to continue: 2

6 5. Accept the license agreement and Next to continue: 6. Select Target Platform as Other (not supported) and Next to continue: 7. Select the root location of the WRWB installation workbench-4\eclipse\x86_64-win32 folder, Next to continue: 8. In the next two steps, separate folders will be selected for C++test installation: One for the C++test Installation directory, and one for the Parasoft Test installation directory. Both are required. 9. Select the C++test destination location: It is highly recommended that you do not use the default location, there are spaces in the path name. Use a location without any spaces or special characters in the path folder names: Eg) C:\Parasoft\desktop\cpptest\

7 10. Next to continue. 11. Select the Parasoft Test destination location, again with no spaces in the path folder names: 12. Next to continue. 13. Select the start menu folder desired and Next to continue 14. Verify location information is correct and click Install to start installation: 15. The installation will create folders specified and install C++test and Parasoft Test files. 16. When complete, click Finish to finalize the installation: 4

8 17. C++test Path The installation folder for C++test must be in the path for the environment WRWB is being run in. You can add the installation folder to your default system path, or add the location to your path in a command window and start WRWB from that window. C++test License For existing customers that currently have C++test licensing, setup licensing the same as you have been. To obtain a license from Parasoft: 1. Start WRWB 4.x in the usual manner and open the C++test perspective. a. Window=>Perspective=>Open Perspective=>Other b. Select Parasoft C++test and OK Note: If you don t see the Parasoft C++test perspective, something is wrong with the installation. 2. Using the top level menu: a. Parasoft=>Preferences=>License b. Set the license type to Local c. The Machine id shown is used for licensing 5

9 i. Log into the Parasoft Customer Portal as described above in the C++test Distribution topic. ii. Fill out the Request License section to obtain your C++test license or contact your Parasoft representative. d. You will get information back from Parasoft License Maintenance with the license data and instructions. e. If using a temp or node locked license, enter the 256 character Password string in the Password field: f. Select Apply and the C++test features enabled by the license will be highlighted and an expiration date will be displayed. C++test Uninstalling To uninstall the C++test Workbench plugin: Use the unins000.exe uninstall executable in the C++test installation directory. Never uninstall C++test plugin by simply removing the files. 6

10 Known Issues There are differences in WRWB 4.x that require adjustment in the way C++test is used within WRWB 4.x The next topics go thru setup and usage of C++test with WRWB 4.x This list will be updated as any known issues surface: 7

11 Configure WRWB for Usage with C++test WRWB Environment Variables The setup in this document will rely on WRWB environment variables being set. You can set these in your default environment; or open a command window, set them, then start WRWB from this environment. 1. WIND_HOME = Base install folder for WRWB set WIND_HOME=C:\WR4.x 2. WIND_BASE = vxworks-7 folder in the WRWB base folder set WIND_BASE=C:\WR4.x\vxworks-7 Configure Project Code Initial project directory setup 3. C++test provides an Examples folder, in the installation directory, containing example projects. 4. This document will use the ATM example project. 5. Create a base directory for the Application Under Test (AUT) Eg) C:\Parasoft\Examples (Base directory can be located anyplace, just use consistently below) 6. The ATM project is configured for usage with Visual Studio and other IDE s. So, we will only copy specific files from the ATM distribution folder for our needs. Configure your BaseDir as below: <BASE_DIR> ATM Account.cxx ATM.cxx Bank.cxx BaseDisplay.cxx include Account.hxx ATM.hxx Bank.hxx BaseDisplay.hxx Note: Source and header files are copied from C++test installation ATM example project. Delete unnecessary files, including the makefile, from the ATM directory is indicated above Create C++test / WRWB Project Start WRWB and set the workspace to <BASE_DIR>\workspace Create a DKM Managed Build project using the ATM example code 1. From the C++test perspective: File=>New=>Project=>Wind River Workbench Project 8

12 Next a) Set Build type: Downloadable Kernel Module Next b) Set Project name: ATM Set Location: Create project in external location Set Directory: C:\Parasoft\Examples\ATM (Or other path used as <BASE_DIR>\ATM) Next c) Set Based on: a source build project 9

13 Set Project: vsb_vxsim_windows (prebuilt) Finish d) Delete the dkm.c project file created: Configure include paths for project a) Select the ATM project in the Navigator b) RtMouse=>Properties c) Open the Build Properties page: d) Open the Paths tab and select Add: e) Set Value: -IC:\Parasoft\Examples\ATM\include (Or other path used: <BASE_DIR>\ATM\include) 10

14 OK f) Select Yes to modifying the slashes if asked: g) Use the Down button to move the new include path to the bottom of the list: h) OK and Yes to rebuilding the Index: Test Build the Project 1. Select the ATM project in the Navigator 2. RtMouse ATM=>Build Project 3. Verify in Build Console output that there are no build errors Configure Project for Using a Build Data File (BDF) C++test 10.3 is currently not fully integrated with WRWB 4.5, so a BDF needs to be created and used for the C++test build information as a workaround. C++test provides a cpptesttrace utility program that will trace the build command processes, capture the compiler/linker arguments passed to the process, and save them into the BDF. This information is then used by C++test to build/link code for analysis. 11

15 For this project, we will use cpptesttrace in conjunction with a command line build to create/update the BDF. The BDF will need to then be modified as a workaround to remove CTOR/DTOR information that interferes with C++test project linking. Setup and Test Project Command Line Build 1. In WRWB, open the Build Console tab. 2. Select the ATM project in the Navigator then clean and build the Project. 3. The Build Console will have information on the command line used to do the build: 4. Open a VxWorks Development Shell: a. Project=>Open Development Shell b. Select VxWorks and OK 5. In the Terminal window opened, go to the Build Target folder: cd C:\Parasoft\Examples\ATM\vsb_vxsim_windows_SIMNTgnu 6. Using the information for the build from above, enter the make command used, remove the JOBS argument and add clean all to the end of the command: make --no-print-directory BUILD_SPEC=vsb_vxsim_windows_SIMNTgnu DEBUG_MODE=1 TRACE=1 clean all 12

16 7. Run the make command and the project should be built with no errors. Run cpptesttrace to Generate the BDF 1. Using the same command line build above, add the cpptesttrace arguments before the make command: cpptesttrace --cpptesttraceprojectname=atm -- cpptesttraceoutputfile=c:/parasoft/examples/atm/cpptest.bdf make --no-printdirectory BUILD_SPEC=vsb_vxsim_windows_SIMNTgnu DEBUG_MODE=1 TRACE=1 clean all Notes: May need to use the full path to cpptesttrace 2. Run the cpptesttrace command and the build should succeed and the BDF generated in the project location (may need to refresh to see the new file created) Edit the BDF to Remove cdtd.c Build Information Again, C++test is not fully integrated with WRWB 4.x and the building of the VxWorks generated ctdt.c causes problems when linking the test executable. As a workaround, the BDF can be modified so that C++test will not include this for the UT build. There are other ways to work around this, but for this example,we will edit the BDF. 1. Open the cpptest.bdf file in an editor 2. Search for ctdt.c and remove this section from the BDF 3. Save the BDF 13

17 4. If you rebuild/update the BDF, this process will need to be repeated. Configure C++test Build Settings 1. Open the Parasoft/C++test/Build Settings page a. Select the ATM project in the Navigator b. RtClick=>Properties c. Expand Parasoft/C++test in the left pane and select Build Settings 2. Set the Options source: Use options from a build data file 3. Set the Build data file: ${project_loc}/cpptest.bdf 4. Under Compiler settings (use the appropriate settings for your compiler/target): a. Family: Wind River GCC 4.3.x b. C compiler: ccpentium c. C++ Compiler: c++pentium d. Linker: c++pentium Notes: If you have a problem finding compiler executables later when running, you can add the full path to the compiler/linker settings above Eg) C:\WR4.x\compilers\gnu \x86-win32\bin\ccpentium Your WRWB compiler should be GCC 4.8.x, but use the GCC 4.3.x family for the purposes of this setup. 5. Apply and OK to exit Project Properties 14

18 C++test Static Analysis (SA) Setup C++test SA test configuration Using the top level Parasoft menu: 1. Parasoft=>Test Configurations 2. Expand Builtin=>Static Analysis 3. RtMouse Effective C++=>Duplicate 4. RtMouse on the User-defined/Static Analysis/Effective C++ configuration and Set Folder to WRWB4 5. Set name: My Effective C++ 6. Apply 7. RtMouse the User-defined/WRWB/My Effective C++ =>Set As Favorite a. Click on top favorite and you should see the red F added to the user configurations icon. 8. Close Run SA on ATM Project SubSubtopics Information. 1. Select the ATM.cxx source file in the Project Navigator 2. Select the blue C++test run icon to run the default configuration 3. The Test Progress tab should show files checked and violations found 15

19 4. Open the Quality Tasks tab in the lower right pane 5. By default, Violations are organized by file. 6. DblClick a file to expand the tree 7. Expand ATM to review Static Analysis results 8. DblClick a Violation to open the sorce file on the violation point 9. Review results 16

20 C++test Unit Testing (UT) Create a target connection for VxSim A Target connection for VxSim is needed to run C++test Unit Tests on the simulator. The default VxWorks7 VxSim does not supply C++ standard library support which is needed for the example project. We will create a custom VxSim as follows: Create VxSim Project 1. Create a working directory for the VxWorks Image in a location where it can be easily found and used by other projects. Eg) C:\Parasoft\VxSim 2. Start workbench and set the workspace to C:\Parasoft\VxSim\workspace 3. From the System Development perspective. 4. File=>New=>Project=>VxWorks 7 expand VxWorks 7 and select VxWorks Image Project 5. Next 6. If you have multiple VxWorks version installed, you may me asked: Target operating system: Wind River VxWorks 7 and Next 7. On Project page: a. Project name: vxsim7 b. Select Create project in workspace c. Next 8. On Project Setup page: a. Setup the project - Based on - an existing project b. Project: vip_vxsim_windows_gnu (prebuilt) 17

21 c. Finish Modify Kernel Configuration and Build VxWorks 1. Expand vxsim7 project in Navigator 2. DblClick Kernel Configuration 3. Expand C++ components in editor 4. RtMouse standard library=>include(quick include) 5. In Project Explorer - RtClick vxsim7=>build Project Capture VxWorks Location of use in Test Configurations 1. In Project Explorer - expand the vxsim7 project and Binaries folder 18

22 2. RtClick vxworks=>properties 3. Capture the Location of the vxworks target for use in the later steps C:\Parasoft\VxSim\workspace\vxsim7\default\vxWorks 4. OK Create test configurations C++test provides builtin test configurations for working with WRWB/VxWorks projects. The builtin configurations provide example configurations for performing the various subtasks associated with running UT in this environment. This document will concentrate on a configuration to generate test cases, and single test configuration to build/run/load results, as the intent is to show setup for using C++test with WRWB 4.x and not the various ways this can be done. After this setup, all the information in the Users Guide on using C++test with WRWB should be applicable. Generate UT one per function configuration C++test can generate example Unit Test Suites and Test Cases for your project. These should be used as a starting point to help develop a testing strategy, setup and run initial test cases, evaluate metrics that need to be collected, review initial code coverage, what code may need to be further tested, etc. It is recommended that you generate one test case per function for this purpose, run these tests, and review results. You will then have a working test suite that you can expand on to drive your UT requirements. 1. Open the C++test test configurations and duplicate the Builtin/Unit Testing/Generate Unit Tests configuration: 2. Set Folder name to WRWB4 19

23 3. Open the User-defined/WRWB4/Generate Unit Tests configuration 4. On the Generation/General tab: a. Change the name to Generate UT one per function b. Change the Max number of generated test cases (per function) = 1 5. On the Generation/Test case tab: a. Check the box for Do not use other initializers for types with factory functions 6. Apply and Close to save changes Run UT DKM on Simulator (Project Scope) configuration There are WRWB builtin test configurations in C++test located in Builtin/Embedded Systems/Wind River/Workbench. We will work here with Downloadable Kernel Module Projects Modification of some of the builtin test configurations is required for working with WRWB 4.x For this document, we will create a single test configuration that will do the following: 1. Library Symbols Identification (LSI) step creating and using the VxWorks symbols list 2. Generate the test runner 3. Compile code 4. Build/compile CTOR/DTOR file 5. Compile Runtime library Code 6. Link the test executable 7. Delete any existing results file on host 8. Generate script to load the test executable 9. Generate script to unload the test executable 10. Run tests on simulator 11. Load and report test results in IDE The above provides a single step running of your Unit Tests. This test configuration can be easily broken up into sub steps if desired. Create the test configuration: 20

24 1. Duplicate the Build VxWorks Test Module - DKM (PassFS) configuration 2. Set Folder to WRWB4 3. Change name to Run UT DKM on Simulator 4. Open the Execution/General tab 5. Select Edit on the right of the Test execution flow line Note: This step provides information on changes to the steps in the test execution flow. This is followed by a full listing of the test execution flow that can be loaded into the test configuration. a. Replace echo messages related to test flow customization with: <Echo msg="this execution flow builds the test exec, loads and runs it, then imports results." b. The next section defines property keys used in the execution flow and whether they are changeable from the test configuration page. Change the property key section as follows: <!-- By default the recipe is set up to the GNU toolchain, you can switch to the DIAB toolchain by commenting/uncommenting appropriate property settings, as well as introducing any other platform specific configuration. --> <SetProperty key="sym_file" value="${cpptest:testware_loc}/libsym.xml" uieditable="false" displayname="path to file with external symbols list" <SetProperty key="nm" value="nmpentium" uieditable="true" displayname="symbols listing tool (GNU: nmpentium DIAB: ddump)" <SetProperty key="nm_opts" value="-g -p --defined-only --no-demangle" uieditable="true" displayname="symbols listing options" <SetProperty key="ctdt_opts" value="-g" uieditable="true" displayname="ctdt extraction options (GNU: -g DIAB -Ng)" <SetProperty key="tcl" value="tclsh" <SetProperty key="jre" value="java" <SetProperty key="munch" value="${wind_base}/host/resource/hutils/tcl/munch.tcl" <SetProperty key="munch_opts" value="-c pentium" <SetProperty key="wrenv" value="${wind_home}\wrenv -p vxworks-7" uieditable="true" displayname="wrs Environment" <SetProperty key="tgtimg" value="${wind_base}\samples\prebuilt_projects\vip_vxsim_windows_gnu\default\vxworks" uieditable="true" displayname="vxworks 7 core file to load" <SetProperty key="tlog" value="${cpptest:testware_loc}/cpptest_results.tlog" uieditable="true" displayname="test results" <SetProperty key="clog" value="${cpptest:testware_loc}/cpptest_results.clog" uieditable="true" displayname="coverage results" 21

25 c. Before the <ReadSymbolsDataStep> add the following two custom steps that will generate the VxWorks symbols file: <CustomStep id="nm" label="extracting symbols..." commandline=""${cpptestproperty:nm}" ${cpptestproperty:nm_opts} "${cpptestproperty:tgtimg}"" workingdir="${cpptest:testware_loc}" result="${cpptest:testware_loc}/libnm.out" stdout="${cpptest:testware_loc}/libnm.out" hidestdout="true" okexitcode="0" <CustomStep id="nm2xml" label="creating external symbols list..." commandline=""${cpptestproperty:jre}" -cp "${cpptest:utils_dir}" LSISymLstGen libnm.out "${cpptestproperty:sym_file}"" workingdir="${cpptest:testware_loc}" result="${cpptestproperty:sym_file}" okexitcode="0" d. After the <LinkStep result=..> add the following lines that will: i. Delete result files on host if they exist ii. Create a script to be use by the target server to load the test executable iii. Create a script to be use by the target server to unload the test executable iv. Load the test executable and run it on the simulator v. Unload the test executable vi. Load test results files into the IDE and report results <RemoveFileStep file="${cpptestproperty:tlog}" <RemoveFileStep file="${cpptestproperty:clog}" <Echo label="generating WindShell script (running tests)..." msg="ld < host:${cpptest:testware_loc}/${project_name}test.out${eol}cpptest_main${eol}reboot(-1)" file="${cpptest:testware_loc}/windsh-run.scr" <Echo label="generating WindShell script (unloading Test Object)..." msg="unld "${project_name}test.out"${eol}reboot(-1)" file="${cpptest:testware_loc}/windsh-unld.scr" <CustomStep id="run_tests" label="running tests..." commandline="${cpptestproperty:wrenv} vxsim -exitonerror -f ${cpptestproperty:tgtimg} -s windsh-run.scr" workingdir="${cpptest:testware_loc}" result="${cpptest:testware_loc}/cpptest_results.tlog" timeouttrackfile="${cpptest:testware_loc}/cpptest_results.tlog" timeoutinfoproperty="test_exec_timeouted" <CustomStep 22

26 id="unload_testobj" label="unloading Test Object..." commandline="${cpptestproperty:wrenv} vxsim -exitonerror -f ${cpptestproperty:tgtimg} -s windsh-unld.scr" workingdir="${cpptest:testware_loc}" <ReadStaticCoverageStep <SendStaticCoverageStep <ReadTestLogStep testlogfile="${cpptestproperty:tlog}" timeoutinfoproperty="test_exec_timeouted" <ReadDynamicCoverageStep covlogfile="${cpptestproperty:clog}" e. Select OK to save results 6. Complete test execution flow: Note: It is suggested that you copy this into a plain text editor such as notepad to help prevent non-displayable characters from getting introduced. Then copy from Notepad and replace the entire contents of the test execution flow in your Run UT DKM on Simulator configuration. <?xml version="1.0" encoding="utf-8"?> <FlowRecipeTemplate toolname="c++test" formatversion="1.0"> <Name>Perform UT (DKM) - File Channel on PassFS (license required)</name> <TestExecutionModeHint>UnitTesting</TestExecutionModeHint> <RunnableExecution> <Echo msg="this execution flow builds the test exec, loads and runs it, then imports results." <!-- By default the recipe is set up to the GNU toolchain, you can switch to the DIAB toolchain by commenting/uncommenting appropriate property settings, as well as introducing any other platform specifc configuration. --> <SetProperty key="sym_file" value="${cpptest:testware_loc}/libsym.xml" uieditable="false" displayname="path to file with external symbols list" <SetProperty key="nm" value="nmpentium" uieditable="true" displayname="symbols listing tool (GNU: nmpentium DIAB: ddump)" <SetProperty key="nm_opts" value="-g -p --defined-only --no-demangle" uieditable="true" displayname="symbols listing options" <SetProperty key="ctdt_opts" value="-g" uieditable="true" displayname="ctdt extraction options (GNU: -g DIAB -Ng)" <SetProperty key="tcl" value="tclsh" <SetProperty key="jre" value="java" <SetProperty key="munch" value="${wind_base}/host/resource/hutils/tcl/munch.tcl" <SetProperty key="munch_opts" value="-c pentium" <SetProperty key="wrenv" value="${wind_home}\wrenv -p vxworks-7" uieditable="true" displayname="wrs Environment" <SetProperty key="tgtimg" value="${wind_base}\samples\prebuilt_projects\vip_vxsim_windows_gnu\default\vxworks" uieditable="true" displayname="vxworks 7 core file to load" <SetProperty key="tlog" value="${cpptest:testware_loc}/cpptest_results.tlog" uieditable="true" displayname="test results" <SetProperty key="clog" value="${cpptest:testware_loc}/cpptest_results.clog" uieditable="true" displayname="coverage results" 23

27 </RunnableExecution> <ConditionalExecution value="${cpptest:os}" equals="windows"> <SetProperty key="host_prefix" value="host:" </ConditionalExecution> <RunnableExecution> <SetProperty key="stub_config_file" value="${cpptest:testware_loc}/stubconfig.xml" <SetProperty key="stub_config_header_file" value="${cpptest:testware_loc}/cpptest_stubconfig.h" <TestCaseFindingStep testsuiteconfigfile="${cpptest:testware_loc}/testsuites.xml" allownotestcasesrun="true" <PrecompileStep <AppendIncludedTestCases <HarnessInstrumentationStep symbolsoptimization="false" <ReadStaticCoverageStep <SendStaticCoverageStep <UserStubsInstrumentationStep <CustomStep id="nm" label="extracting symbols..." commandline=""${cpptestproperty:nm}" ${cpptestproperty:nm_opts} "${cpptestproperty:tgtimg}"" workingdir="${cpptest:testware_loc}" result="${cpptest:testware_loc}/libnm.out" stdout="${cpptest:testware_loc}/libnm.out" hidestdout="true" okexitcode="0" <CustomStep id="nm2xml" label="creating external symbols list..." commandline=""${cpptestproperty:jre}" -cp "${cpptest:utils_dir}" LSISymLstGen libnm.out "${cpptestproperty:sym_file}"" workingdir="${cpptest:testware_loc}" result="${cpptestproperty:sym_file}" okexitcode="0" <ReadSymbolsDataStep <LsiStep libsymfile="${cpptestproperty:sym_file}" <ReadLsiConfigStep <AnalyzeMissingDefinitions generatestubs="false" <ConfigureStubs <CreateStubConfigHeader <PrepareDataSources type="array" <TestRunnerGenerationStep testsuiteconfigfile="${cpptest:testware_loc}/testsuites.xml" testrunnercfile="${cpptest:testware_loc}/cpptest_testrunner.c" 24

28 testrunnercppfile="${cpptest:testware_loc}/cpptest_testrunner.cpp" testlogfile="${cpptestproperty:host_prefix}${cpptest:testware_loc}/cpptest_results.tlog" covlogfile="${cpptestproperty:host_prefix}${cpptest:testware_loc}/cpptest_results.clog" appendlogs="false" <CompileStep <CustomStep id="ctdt_nm" label="ctdt Generation - extracting symbols..." commandline=""${cpptestproperty:nm}" ${cpptestproperty:ctdt_opts} ${cpptest:test_objects_quoted}" workingdir="${cpptest:testware_loc}" stdout="${cpptest:testware_loc}/ctdt_nm.out" result="${cpptest:testware_loc}/ctdt_nm.out" bypassconsole="true" dependencyfiles="${cpptest:test_objects_quoted}" <CustomStep id="ctdt_munch" label="ctdt Generation - munching..." commandline=""${cpptestproperty:tcl}" "${cpptestproperty:munch}" ${cpptestproperty:munch_opts}" workingdir="${cpptest:testware_loc}" stdin="${cpptest:testware_loc}/ctdt_nm.out" stdout="${cpptest:testware_loc}/ctdt.c" result="${cpptest:testware_loc}/ctdt.c" dependencyfiles="${cpptest:test_objects_quoted}" <CompileStep file="${cpptest:testware_loc}/ctdt.c" addtoextsources="true" <BuildRuntimeLibStep ignoredbgopts="true" <LinkStep result="${cpptest:testware_loc}/${project_name}test.out" <RemoveFileStep file="${cpptestproperty:tlog}" <RemoveFileStep file="${cpptestproperty:clog}" <Echo label="generating WindShell script (running tests)..." msg="ld < host:${cpptest:testware_loc}/${project_name}test.out${eol}cpptest_main${eol}reboot(-1)" file="${cpptest:testware_loc}/windsh-run.scr" <CustomStep id="run_tests" label="running tests..." commandline="${cpptestproperty:wrenv} vxsim -exitonerror -f ${cpptestproperty:tgtimg} -s windsh-run.scr" workingdir="${cpptest:testware_loc}" result="${cpptest:testware_loc}/cpptest_results.tlog" timeouttrackfile="${cpptest:testware_loc}/cpptest_results.tlog" timeoutinfoproperty="test_exec_timeouted" <Echo label="generating WindShell script (unloading Test Object)..." msg="unld "${project_name}test.out"${eol}reboot(-1)" file="${cpptest:testware_loc}/windsh-unld.scr" 25

29 <CustomStep id="unload_testobj" label="unloading Test Object..." commandline="${cpptestproperty:wrenv} vxsim -exitonerror -f ${cpptestproperty:tgtimg} -s windsh-unld.scr" workingdir="${cpptest:testware_loc}" <ReadStaticCoverageStep <SendStaticCoverageStep <ReadTestLogStep testlogfile="${cpptestproperty:tlog}" timeoutinfoproperty="test_exec_timeouted" <ReadDynamicCoverageStep covlogfile="${cpptestproperty:clog}" </RunnableExecution> <FinalizeExecution> <ClearTempCoverageData </FinalizeExecution> </FlowRecipeTemplate> 7. After configuring the test execution flow, you will see the UI editable variables in the Test Execution Flow list. 8. Change the VxWorks 7 core file to load variable to the path captured above for VxSim image created. 9. Verify that they are set as below: 10. Apply to save changes and close 26

30 Generate Unit Tests Generate Test Suite and Test Cases for the ATM.cxx class From this point, normal generation and running Procedures can be used to perform UT. For this document, we will generate a test case for each of the functions in the ATM.cxx class 1. Select ATM.cxx in the Navigator 2. Parasoft=>Test Using=>User-Defined=>WRWB4=>Generate UT one per function 3. The test progress tab should show on TestSuite and 3 Test Cases created. Exclude Unit Tests folder from Project Build When the normal Project builds, you will get errors on the newly added test folder contents. This folder needs to be excluded from the build for the project and will only be used by C++test. 1. Open the System Development perspective. 2. Expand the ATM project Build Targets folders to expose the tests folder in the project 3. RtClick=>Exclude from Build Target and Yes to complete action: Run Unit Tests 1. Open the Parasoft C++test perspective 2. Open the Test Case Explorer tab 3. Expand the ATM tree to expose the Test Suite and contents generated 4. Select the Test Suite 5. Parasoft=>Test Using=>User-Defined=>WRWB4=>Run UT DKM 0n Simulator 27

31 6. You can monitor the Console output for test run progress. 7. You will see pop-up windows, that go away when complete, as the Simulator runs. 8. The Test Progress tab and Test Case Explorer will show the pass/fail results of the test cases. 9. You can open the Coverage tab and review/navigate to decorated code. Note: If you get errors when running, it may be due to not setting the WRWB environment variables WIND_HOME and WIND_BASE as instructed earlier. Check these. Summary You should now be able to use the test configuration created to run other UT on this project or configure and run on other projects. If there is a need to only build the test executable and run it separately, the Run UT DKM on Simulator test configuration can be duplicated and configured for separate operations. Likewise, the processes described here can be used for RTM, VIP, and other project types. 28