Question keys are created in the following form:
interview-class-name.question-name
■The .smry entry specifies the question title (in the example, Feature Support) that the Configuration Editor displays to the user.
■The .text entry specifies the question text (in the example, Does your system support the feature that ... ?) that the Configuration Editor displays to the user.
4.Create a More Info topic file for the question.
The More Info system of the Configuration Editor displays topic files for each question. Each file provides detailed information that the user needs when answering its associated interview question. Refer to Chapter 6 in the JavaTest Architect’s Guide for additional information about creating More Info topic files.
Examples of More Info topic files can be found in the following
SampleTestSuite location.
AdvancedTestSuite/sampletck/src/sample/suite/help/default/SampleInterview/
5.Update the map file.
After the topic file is created, the map file must be updated.
If the topic file for the new question is named featureSupport.html, the test developer must add the following line to the sampleInterview.jhm file.
<mapID target="SampleInterview.featureSupported" url="SampleInterview/featureSupport.html"/>
Note – The sampleInterview.jhm map file is located in the
AdvancedTestSuite/sampletck/src/sample/suite/help/default/
directory.
6.Create the JAR file.
After creating the interview, you must package it into a JAR file for inclusion with the test suite during the build time.
If you successfully ran the build as described in Chapter 2, “Building an Updated Simple Test Suite” on page 19, you have an example of this JAR file under the lib directory. In the example, the JAR file is named
AdvancedTestSuite/lib/sample_jt.jar.
7.Add the JAR file to the classpath entry of the testsuite.jtt file.
The test suite containing the configuration interview and associated tests can now be built. See “Building a Test Suite” on page 40, in Chapter 3.
