Lesson 2 – Creating a Test Method
If the first testmethod-based test suite does not have the CONNECT
API, the
testfunction must be executed before the first
connect
testmethod-based test suite in a test flow. In addition, if the
testfunction is executed in a test flow and if there is a
disconnect
testmethod-based test suite later, a test suite that executes the
testfunction must be used between the test suites.
connect
The following figure shows a typical directory structure for
creating test method programs:
Device Directory
User-defined Directory
Project1
Project1.cpp
Project1.h
Project1.dsw
Project1Tlb.cpp
Project1_i.cpp
MyClass1.cpp
MyClass1.h
MakefileDBG
<file_name>~
Debug
Directory Structure
In the above figure, to create a shared library, the
directory is first created as a project. Then, class source files,
header files, and configuration files required for the shared library
are created under the directory.
If you compile a test method program after you develop it, the
source and header files are compiled and linked according to
, and the shared library and object files are created
MakefileDBG
under the
directory.
Debug
The following shows the development flow of test method
programs:
434
(Directory for test method environment, Default: TestMethod)
(Project directory in which a shared library is stored)
(System auto-generated files)
(Class source file)
(Class header file)
(Makefile to generate a shared library)
(Backup files)
(Directory in which object files and the shared library are stored)
MyClass1.o
(Class object file)
Project1.o
(Library object file)
Project1.sl
(Test Method shared library)
Project1