GUI Capture - Revision history

Manus: /* Low Level Hooks */

2011-02-14T22:31:18Z

‎Low Level Hooks

2006-11-02T18:09:23Z

‎Eiffel Level Hooks

2006-11-02T01:47:04Z

‎Sidenote

2006-11-02T01:43:11Z

2006-11-01T23:30:23Z

2006-11-01T19:45:49Z

2006-10-31T22:43:48Z

New page

==Overview==

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

@@ Line 11: / Line 11: @@
 ===Low Level Hooks===
-On Windwos it is possible to capture low level window events. Through these it is possible for a capturing tool to launch the AUT and then install a hook to receive all input events. This should also be the case for Unix although it is not checked yet.
+On Windows it is possible to capture low level window events. Through these it is possible for a capturing tool to launch the AUT and then install a hook to receive all input events. This should also be the case for Unix although it is not checked yet.
 ;Pro

@@ Line 22: / Line 22: @@
 ===Eiffel Level Hooks===
-For Vision2 we could implement a ''capturing mode''. When this mode is activated, all events - including focus-chaning events or other higher level events - could be exported to a file. The implementation would mainly be done in the underlying toolkit (WEL and GTK implementation).
+For Vision2 we could implement a ''capturing mode''. When this mode is activated, all events - including higher level events if needed - could be exported to a file. The implementation would mainly be done in the underlying toolkit (WEL and GTK implementation).
 ;Pro

← Older revision		Revision as of 01:47, 2 November 2006
Line 33:		Line 33:
	==Sidenote==		==Sidenote==

−	If event capturing is implemented into Vision2 it could be used to generate bug reports for EiffelStudio ~~from users~~ by sending in their event sequence. Of course it remains to check how large an event sequence gets after some time of using EiffelStudio.	+	If event capturing is implemented into Vision2 it could be used to generate bug reports for EiffelStudio by sending in their event sequence which led to the problem. Of course it remains to check how large an event sequence gets after some time of using EiffelStudio.

← Older revision		Revision as of 01:43, 2 November 2006
Line 30:		Line 30:
	* Event recording and its activation is part of the AUT		* Event recording and its activation is part of the AUT
	* Only Vision2 can be captured		* Only Vision2 can be captured
		+
		+	==Sidenote==
		+
		+	If event capturing is implemented into Vision2 it could be used to generate bug reports for EiffelStudio from users by sending in their event sequence. Of course it remains to check how large an event sequence gets after some time of using EiffelStudio.

@@ Line 3: / Line 3: @@
 ==Overview==
-TODO
+During the recording of a test case, all events of the AUT are recorded for later replay.
 ==Approaches==
@@ Line 28: / Line 28: @@
 * Additional information is available (e.g. widget name)
 ;Contra
-* Activating capturing is part of the AUT
+* Event recording and its activation is part of the AUT
 * Only Vision2 can be captured

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

−	~~Not~~ yet ~~available~~. ~~See [[GUI Capture~~ (~~Developement~~)]]	+	TODO
		+
		+	==Approaches==
		+
		+	There are different approaches for capturing GUI events:
		+
		+	===Low Level Hooks===
		+
		+	On Windwos it is possible to capture low level window events. Through these it is possible for a capturing tool to launch the AUT and then install a hook to receive all input events. This should also be the case for Unix although it is not checked yet.
		+
		+	;Pro
		+	* Capturing tool and AUT are separate
		+	* Can capture events from any application
		+	;Contra
		+	* Only receive low level events. No information about focus-changing for example.
		+	* Unclear how to receive additional information about AUT like current active widget or widget name of clicked widgets
		+
		+	===Eiffel Level Hooks===
		+
		+	For Vision2 we could implement a ''capturing mode''. When this mode is activated, all events - including focus-chaning events or other higher level events - could be exported to a file. The implementation would mainly be done in the underlying toolkit (WEL and GTK implementation).
		+
		+	;Pro
		+	* Capturing of all events
		+	* Additional information is available (e.g. widget name)
		+	;Contra
		+	* Activating capturing is part of the AUT
		+	* Only Vision2 can be captured