Have a look at the right side of your screen. This is the Project Explorer window, and within it two tabs are visible.
The first - the Project Browser tab - contains a reference to all group, application and test nodes created for the active project. The project node, named MyProject, contains an application node named MyApplication; the application node contains a list of all of the source files required to build the application.
The second tab - the Asset Browser tab - lets you browse all of your source files and test scripts. If the selected Sort Method is By File, you are presented with a file-by-file listing of test scripts and source code. Note how each source file can be expanded to display every defined package or function. Double-clicking any test script or source file node will open its contents in the OneTest Embedded editor; double-clicking any package node will open the relevant source file to the very line of code at which the definition or declaration occurs.
There are two other sort methods as well on the Asset Browser. The first, By Object, lets you filter down to packages, independently of the source files. The second, By Directory
You may have noticed along one of the toolbars at the top of the UI that the TDP you selected in the New Project Wizard is listed in a dropdown box. In fact, this is not a reference to the TDP, it is a reference to the Configuration whose base TDP was the one you selected in the wizard - in the case of this tutorial, it is a TDP supporting Ada. Configurations are initially named after their base TDP, but this name can be changed. Should you have multiple configurations for the same project, use this dropdown box to select the active Configuration for execution.
Finally, to the right of the Configuration dropdown list is the Build button. This button is used to build your application for application nodes and the test harness for test nodes.
Armed with this knowledge, proceed to Exercise Two.