Test Attributes
The test attributes specify the properties or characteristics the test assumes during its execution. The following describes these properties, their possible values, and how tests with these properties are affected.
Attributes |
Specifies… |
Title |
Title entered when creating the test information object in the Workbench |
Test category |
Test category chosen when creating the test information object in the Workbench |
Introduction title |
Information object with category Introduction created to be used for test instructions as well as for general operational instructions for the test player. You add the instructions to the test by dragging the introduction info object and dropping it on the Introduction Title field in the Knowledge Workbench. For an example of an introduction info object, see Introduction Template. |
Use test form |
Test forms to be used for test execution |
Organizational criteria |
Elements of the configured test structure, that is sub-tests and performance units, to be used in a test. If you decide not to use a structure, the test simply consists of a number of items that can be placed in any position within the test. If the test contains structure elements that are sub-tests only and not performance units, the sub-test items can be placed in any position under their corresponding sub-test. If the test contains both sub-tests and performance units as structure criteria, the performance units can be placed in any position under their corresponding sub-test. In this case, the performance unit items can be placed in any position under their corresponding performance unit. The same applies if the test contains only performance units and no sub-tests.
If the structure elements of the configured test structure are not saved as structure criteria in the test, the test still retains all characteristics of the test elements it contains. For example, if you created a test with sub-tests that are not specified as structure criteria, the test is not structured by sub-tests in the player, although the test retains the characteristics specified for the sub-tests, such as evaluation and feedback at sub-test level. |
Display test structure |
Whether the test structure is displayed in the player during test execution |
Save test results |
Whether individual test results are saved |
Maximum test time (min.) |
Maximum time available to complete the test in minutes. The test time is displayed as remaining time in the player. The test start, possibly after completion of an introduction, is also the start of the test time. When the test time has run out, the test is automatically ended and no further entries are accepted.
A value of zero for this attribute specifies that the test has no time limit. |
Dynamic item selection |
Whether test items can be selected dynamically from the test form (attribute: Yes) or only in the sequence defined in the test form (attribute: No). Dynamic selection of test items occurs in the player during test execution. The attribute values Test, Sub-Test, or Performance Unit determine the item groups from which items are randomly selected for the test form. The number of possible item groups depends on how the test form is structured. |
Item count |
Number of pooled items at test level that are to be randomly chosen from the test form |
Random order |
Random ordering of sub-tests, performance units, items, and answer alternatives at test execution. The attribute value Answer alternatives specifies that the answers for each item in the test should be randomly ordered. The attribute values Item, Performance unit, and Sub-test specify that the respective structure element should be randomly ordered within the next highest node of the test form structure. For example, if a test form has sub-tests and no performance units and you select attribute value Item, the items within a sub-test are displayed in random order. |
Participant remarks |
Whether participants can add remarks for each item after the test is completed If remarks are allowed, the participant accesses a text editor by choosing Remarks from the player. The remarks are saved with the participant test results. Participant remarks can provide important information about how effective tests and test items are especially during beta testing phase. |
Scoring model |
Model to be used by which the individual test results are scored The value Standard specifies that each correct test item receives exactly one point in score, which means that the maximum attainable test score is equal to the sum of all items in the test. You can adjust the score weight for individual items with the Item weight attribute. SAP recommends the standard setting for practical and test theoretical reasons. If you select Answer weight, the weights you set in the item editor for individual answer alternatives are used. Scoring models and how they effect test scoring are documented in the item format templates that allow answer weighting. |
Scoring process |
Whether individual test values of all items in the test are scored using only beta items or using only released items with no beta items. You can test beta items by distributing them in a released operational test. This attribute allows you to gather empirical test data for items that are not yet released. |
Cut-off value in % |
Whole-number test value that must be achieved to pass the test, as a percentage If no passing criterion is required, enter a value of zero. |
Feedback level |
Feedback level of detail The participant receives feedback for the test once completed. Depending on the test structure, you can specify that feedback for participants is provided at test, sub-test, performance unit, item, and individual answer levels. Templates are available for feedback at test, sub-test, and performance unit levels. For more information, see the attribute Feedback template title. These templates are specified for each test through the attributes Feedback test passed, Feedback test failed, Feedback web link, and Feedback info object link. If you select these levels, the feedback appears as an HTML page on the participant’s screen once the test is complete. You enter feedback text for items as an attribute in the item editor. If you want the participant to compare his answers with the correct answers in addition to or instead of seeing the feedback text, you must select the attribute value Answer. The participant can view the item feedback as the test is displayed again with feedback information. |
Feedback test passed |
Text in the Feedback template title used when successful completion feedback is provided at the specified level |
Feedback test failed |
Text in the Feedback template title used when unsuccessful completion feedback is provided at the specified level |
Feedback Web link (URL) |
Web link or URL used in the Feedback template title The web link enables the participant to access a web page directly from the test, sub-test, or performance unit feedback, for example to find more information about a particular subject where he lacks knowledge. |
Feedback info object link |
Link to an info object in the Knowledge Warehouse used in the Feedback template title The info object link enables the participant to access information from the training, documentation, or administration areas of the Knowledge Warehouse directly from the test, sub-test, or performance unit. |
Feedback template title |
Title of test-specific templates for feedback at test, sub-test, and performance unit level ( Feedback Template A and Feedback Template B)You add the feedback template to the test by dragging the feedback template info object and dropping it on the Feedback template title field in the Knowledge Workbench. For more information about creating feedback, see Test Feedback Creation. |
Use feedback intervals |
Whether feedback intervals defined in the scoring table are to be used for the test If this is the case, the feedback text for the interval is displayed together with the participant test score. |
Scoring table |
Feedback intervals to provide various feedback texts for defined scoring areas Proceed as follows:
|
