Difference between revisions of "GUI Testing/Test Case generation"
(→Overview) |
(→Overview) |
||
| Line 4: | Line 4: | ||
For the captured sequence of events to become a test case, assertions have to be inserted into the event sequence. These have to be checked when the sequence is executed by the replay tool. | For the captured sequence of events to become a test case, assertions have to be inserted into the event sequence. These have to be checked when the sequence is executed by the replay tool. | ||
| − | How the test case has to be specified depends on the format of the event sequence. If the capturing tool creates an Eiffel file which can be used to replay the sequence, the tester just has to include assertion statements into this file. | + | How the test case has to be specified depends on the format of the event sequence. If the capturing tool creates an Eiffel file which can be used to replay the sequence, the tester just has to include assertion statements into this file. If the event sequence is stored as an xml file the assertions have somehow to be specified externally (e.g. through a scripting language or Eiffel code). The test case is then made up of these two files. |
Latest revision as of 15:23, 1 November 2006
Overview
For the captured sequence of events to become a test case, assertions have to be inserted into the event sequence. These have to be checked when the sequence is executed by the replay tool.
How the test case has to be specified depends on the format of the event sequence. If the capturing tool creates an Eiffel file which can be used to replay the sequence, the tester just has to include assertion statements into this file. If the event sequence is stored as an xml file the assertions have somehow to be specified externally (e.g. through a scripting language or Eiffel code). The test case is then made up of these two files.
