Building a Rock-Solid Content Pipeline with the COLLADA Conformance Test Suite - Game Development Tool Essentials - page 67

The FApplication Script as a Model
The FApplication script in the Scripts directory provides useful information about methods, input, and output.
Note the imported libraries:

• os (a Python module)

• os.path (a Python module)

• subprocess (a Python module)

C:\CTS\Core\Common directory). Gets and replaces
filename extensions; determines whether a filename extension is that of an image file;
determines whether a filename is a proper filename; gets directory names and paths; parses
dates; and so on.

• Core.Common.FUtils (resides in the

•
Class FApplication is the abstract class for the target application. The class defs can be found in the COLLADA
CTS Tutorial.

Core.Common.FConstants (defines the constants the scripts use)

Creating and Running the Tests
To start the test suite GUI, click the Python script COLLADATestSuite.py in the CTS root directory. Before you can run
the tests for the first time, you must populate the test grid as follows:

• Create a new test procedure (File menu)

• Open the procedure you just created (File menu)

• Add tests (Test menu)

To run the tests with an existing procedure, just select File ➤ Open Test procedure, and the full test grid will appear.

Creating a Test Procedure
A test procedure comprises a series of tasks, some of which are repeated: import, export, render, and validate. Each
task can generate one or more COLLADA documents and/or images. You must create and configure a test procedure
before you can run any tests. Test procedures can be reused.
The input to a procedure is one or more data sets, which are found in the StandardDataSets subdirectory of the
CTS hierarchy.
To create a new test procedure, select File ➤ New Test Procedure, and fill in the title: <Product Name> CTS Submission.
For Trimble SketchUp, for example, your procedure name might be SketchUp_CTS_Submission. (Some test procedure
names will not work with spaces.)
In the Add Operation box, select each of the tasks in the order specified here (which is not necessarily the order
in which the operations appear in the box):

• Import ➤ <ProductName> ➤ Add. Import is the only task that requires a product name. The

product name will appear in the right-hand window. (When you run the integration script, the
name of your application will be added to the Import drop-down box.) See Figure 6-1 .