Now that you have created a project, it is time to specify:
your development project's source files
the type of testing or runtime analysis activity you would like to perform first
To start a new activity:
Once a project has been created, the user is automatically brought to the Activities page. In this tutorial you are starting with a focus on runtime analysis functionality, so select the Runtime Analysis link. This will bring up the Runtime Analysis Wizard.
In the window entitled Application Files, you must list all source files for your current development project. For this tutorial, you will directly select the source files. Click Add .
Browse to folder into which you have installed OneTest Embedded and then access the folder \examples\BaseStation_C\src
All C++ and Header Files in the Files
of Type dropdown box is selected, then select all of the C and
C++ source files. Now click the Open
You should see a set of .c, .cpp and .h files listed in the large listbox of the Application Files window.
At this time, an analysis engine parses each source file - referred to as tagging. This process is used to extract the various functions, methods, procedures and classes located within each source file, simplifying code browsing within the UI.
In the window entitled Selective Instrumentation you have the ability to select those functions, procedures, methods or classes that should not be instrumented for runtime analysis. Such selective instrumentation ensures that the instrumentation overhead is kept to a minimum. For this Tutorial, you will be monitoring everything and thus all items should be checked. This should happen by default; if not, click Select All . Click Next.
You have now reached the window entitled Application Node Name. Enter the name of the application node that will be created at the conclusion of the Runtime Analysis Wizard; since you will be monitoring execution of the UMTS base station, type the word BaseStation within the text field labeled Name.
The Application Node Name window also gives you the opportunity to modify build settings associated with the TDP you selected when creating the OneTest Embedded project. Some changes may need to be made, depending on your operating system. (Note that these changes do not affect the actual TDP; you will be making changes to a Configuration. A Configuration lets you modify a variety of settings on a node-by-node basis within a project.
Select the button on the bottom of the Application Node Name window entitled Configuration Settings.
In the window that has just appeared, named Configuration Settings, expand the Build node in the tree on the left-hand side and left-click the Compiler node.
In the Compiler flags edit box on the right-hand side of the window, add the flag -MLd to the end of the list, separated by a space from the flag -GR
In the Preprocessor macro definitions edit box, add the macro _DEBUG (make sure to include the preceding underscore, and use only capital letters).
Select the OK button on the bottom of the window.
You are now confronted with the Summary window. Everything should be in order, so click the Finish button.
The BaseStation application node has now been created. The Project Browser tab of the Project Explorer window should appear as follows: