GUI Replay - Revision history

Juliant: /* Windows messaging system */

2006-11-02T18:32:22Z

‎Windows messaging system

2006-11-02T17:47:01Z

‎Problems

2006-11-01T23:52:46Z

2006-11-01T23:39:15Z

2006-11-01T23:32:49Z

‎Overview

2006-11-01T23:22:47Z

2006-11-01T18:10:52Z

2006-11-01T01:20:30Z

New page

==Overview==

Not yet available. See [[GUI Replay (Developement)]]

@@ Line 28: / Line 28: @@
 ====Windows messaging system====
-On Windows can retreive data from another window by sending it a message (e.g. WM_GETTEXT to a edit field). Through this mechanism you could retreive the data from single widgets. Unfortunatly only native window widgets are supported by this. For example the EiffelStudio editor is natively a drawing panel and thus no meaningful data can be retreived from it.
+On Windows one can retreive data from another window by sending it a message (e.g. WM_GETTEXT to an edit field). Through this mechanism you could retreive the data from single widgets. Unfortunatly only native Windows widgets are supported by this. For example the EiffelStudio editor is natively a drawing panel and thus no meaningful data can be retreived from it.
 ====Screenshot comparison====

@@ Line 25: / Line 25: @@
 If some means of interprocess communication exist, one could think of a protocol to get the current state of the AUT. The test could use this to check the assertions.
 ====Screenshot comparison====
@@ Line 48: / Line 52: @@
 | Testprogram and AUT are completly separate
 | Unclear how to provide interprocess communication in Eiffel
 |-
 | Screenshot comparison

@@ Line 12: / Line 12: @@
 ===Checking assertions===
-To check assertions the test has to access the current state of the AUT. In Eiffel this is a problem since no mechanism for this exist.
+To check assertions the test has to access the current state of the AUT. In Eiffel this is a problem since no mechanism for this exist. Multiple solutions to check assertions exist:
-The closest you get is the debugger which can access non-finalized applications and read the current state as well as execute expressions.
+====Use Debugger====
 {| border="1" cellpadding="5" cellspacing="0" align="center"
@@ Line 21: / Line 37: @@
 ! Method !! Pro !! Contra
 |-
-| Use debugger which can access non-finalized applications
+| Use debugger
 | Testprogram and AUT are completly separate
 | Can only debug non-finalized applications
@@ Line 29: / Line 45: @@
 | Each test (or a group of tests) has to be compiled together with AUT
 |-
-| Provide interprocess communication
+| Interprocess communication
 | Testprogram and AUT are completly separate
 | Unclear how to provide interprocess communication in Eiffel

@@ Line 12: / Line 12: @@
 ===Checking assertions===
 To check assertions the test has to access the current state of the AUT. In Eiffel this is a problem since no mechanism for this exist.
-The closest you get is by the debugger which can access non-finalized applications and read the current state as well as execute expressions.
+The closest you get is the debugger which can access non-finalized applications and read the current state as well as execute expressions.
 {| border="1" cellpadding="5" cellspacing="0" align="center"
@@ Line 25: / Line 25: @@
 | Can only debug non-finalized applications
 |-
-| Compile test together with AUT
+| Compile test into AUT
 | Easy to access state of AUT
 | Each test (or a group of tests) has to be compiled together with AUT
@@ Line 32: / Line 32: @@
 | Testprogram and AUT are completly separate
 | Unclear how to provide interprocess communication in Eiffel
 |}

@@ Line 3: / Line 3: @@
 ==Overview==
-In the replay phase a recorded sequence of events is replayed and the inserted assertions are checked. The desired behaviour is as follows:
+In the replay phase a recorded sequence of events is replayed and the assertions are checked. The desired behaviour is as follows:
 * The test cases can be compiled separate from the AUT.
 * The AUT can be in finalized mode.

@@ Line 1: / Line 1: @@
 [[Category:Testing]]
 ==Overview==
-Not yet available. See [[GUI Replay (Developement)]]
+In the replay phase a recorded sequence of events is replayed and the inserted assertions are checked. The desired behaviour is as follows:

← Older revision		Revision as of 18:10, 1 November 2006
Line 1:		Line 1:
		+	[[Category:Testing]]
	==Overview==		==Overview==

	Not yet available. See [[GUI Replay (Developement)]]		Not yet available. See [[GUI Replay (Developement)]]