By default, test modules present a template that assists you in creating well-formed
tests, ones that conform to the Action Based Testing methodology.
The test module is the work file in which you create tests. Its essence
is to contain a group of test cases with a similar, and if possible narrowly-defined, scope.
A TestArchitect project is typically comprised of multiple
test modules, which are often grouped into folders and subfolders of the project. Test
modules should be designed to run independently from each other, while the test cases within
a test module can have dependencies among themselves.
The test module template
Upon creation, TestArchitect populates the test module with headings for a recommended
Tip: Test modules should be designed to run independently from each
other, while the test cases within a test module can have dependencies among themselves.
- The TEST MODULE heading: As a documentary line, this heading
is fixed at row 1, and is the only non-optional, non-deletable heading in a test
- The OBJECTIVES heading: The OBJECTIVES section holds every
objective that is associated with the test cases. The objectives listed in it define the
scope of the test module. They allow readers to understand why test cases are designed
the way they are, and give an auditor a quick insight into the correctness and, more
importantly, completeness of a test.
built-in action is allowed
to appear in the OBJECTIVE section. Otherwise, the following error dialog box appears.
- The INITIAL heading: The INITIAL section of
a test module is useful for holding action lines that are required for initialization of
the test, especially when such initialization is required for all or most of the test
cases in the module. For example, lines for launching the application under test,
initializing it, etc., would typically appear here.
TEST CASE heading. This is a representative heading, accompanied by a
representative test objective line, both of which are presented as a reminder of
their utility. Typically, your test might have multiple test cases, each of which may
have one or more test objectives associated with it.
Before entering the test objectives of a test case
under the TEST CASE
heading, you must document all test objectives of your test
under the OBJECTIVES
heading. Otherwise, the below error dialog box appears.
- A FINAL heading. Any warranted cleanup operations upon test
completion, such as closing the application under test, would typically appear
A typical test module should resemble the following:
Of the above, INITIAL
, TEST CASE
, and TEST OBJECTIVE
are all built-in actions. They are not,
however, executed at run time. Instead, they serve two purposes:
- First, they serve a documentary and organizational function. This is especially true
of TEST CASE and TEST OBJECTIVE, which specify
the roles of sections of your action lines in the context of an overall test plan.
- Second, the INITIAL, FINAL, and TEST CASE actions serve as entry points for
execution. At the start of your execution run, you may specify exactly which of these
sections of action lines are to be included in the run.
If you do not follow the recommended test module template, as discussed above, a warning
dialog box appears when you save your test module. You may ignore the warning dialog box by
clicking the Continue Anyway button.