Squish groups tests into test suites and test cases: test suites are a container for the test cases, whereas test cases contain the test scripts. One test suite defines certain settings that are used for all test cases it contains, like the application that is started for executing the test.

So first we have to create a new test suite: start the Squish IDE and open the new test suite wizard with File|New Test Suite (Ctrl+Shift+N):

In the first wizard page, you have to enter a name for the test suite and a directory where the test suite is generated. Squish requires that a test suite's name starts with the prefix suite_. But it ensures this automatically, so it is sufficient to enter just the name - currencyconverter in our case.

In the treeview you have to choose a directory where the test suite is stored.

	Note
	Squish organizes test suites, test cases and all other data belonging to a test suite in text files in a directory named suite_<name>. By doing so, it is easily possible to check tests into a source control system or edit tests outside the Squish IDE.

Press Next to get to the next wizard page:

In this page you must select the toolkit your application uses. For testing a Four J's GDC application, choose GDC.

On the next page, you have to choose the scripting language you want to use for writing your tests. In this example we use Python - the other scripting languages work very similar.

On the last wizard page, you have to select the application under test (AUT). For testing Four J's GDC based programs, this is always the gdc application. The first time you create a new test suite, you have to add the application with its full path: click the browse button () and choose the path to the gdc binary.

Once gdc is registered as an application, you can simply select it in the Application combobox.

Click the Finish button now and the Squish IDE displays the newly created test suite. The suite contains some subitems: an item for the object map (see Object Map (Section 16.9)), an item for shared test data and shared scripts (see How to Create and Use Shared Data and Shared Scripts (Section 15.4)) and an item for listing the results of previous test runs.