GUI Testing/Test Case generation - Revision history

Juliant: /* Overview */

2006-11-02T00:23:45Z

‎Overview

Juliant: /* Overview */

2006-11-01T23:32:15Z

‎Overview

Juliant at 20:03, 1 November 2006

2006-11-01T20:03:09Z

New page

[[Category:Testing]]
==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.

The main focus lies on how the event sequence is available. 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.

← Older revision		Revision as of 00:23, 2 November 2006
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.

← Older revision		Revision as of 23:32, 1 November 2006
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.

−	~~The main focus lies~~ on ~~how~~ the event sequence ~~is available~~. 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.