How Testing Tool Works - Revision history

Larryl: /* Test case execution */

2008-04-22T14:42:16Z

‎Test case execution

Larryl: /* Main ideas */

2008-04-22T14:42:01Z

‎Main ideas

Larryl at 13:39, 22 April 2008

2008-04-22T13:39:54Z

Larryl: /* Test case creation */

2008-04-22T13:25:52Z

‎Test case creation

Larryl at 13:25, 22 April 2008

2008-04-22T13:25:31Z

Larryl at 13:14, 22 April 2008

2008-04-22T13:14:36Z

Larryl at 09:20, 21 April 2008

2008-04-21T09:20:17Z

Larryl at 09:18, 21 April 2008

2008-04-21T09:18:55Z

New page

This page explains how Eiffel Studio testing tool works under the hood. For Eiffel Studio testing tool general information, please see [[Eiffel_Testing_Tool]].

@@ Line 24: / Line 24: @@
 If launch success, eweasel output analyzers ({ES_EWEASEL_RESULT_ANALYZER}) will analyze all eweasel console outputs which redirected by process library. The {ES_EWEASEL_RESULT_ANALYZER} manage a set of {ES_EWEASEL_RESULT_HANDLER}s. The responsibility of {ES_EWEASEL_RESULT_ANALYZER} is try to find eweasel test run result output sections, and invoke all {ES_EWEASEL_RESULT_HANDLER} to handle the eweasel output. The eweasel result output section means the text block between two "Test " tags.
 {ES_EWEASEL_RESULT_HANDLER} is using chain of responsibility pattern. So different {ES_EWEASEL_RESULT_HANDLER} descandent will handle different eweasel output case. Such as {ES_EWEASEL_PASSED_RESULT_HANDLER} will try to find if there is ": passed" in a eweasel output section. If found, {ES_EWEASEL_PASSED_RESULT_HANDLER} will create a {ES_EWEASEL_TEST_RESULT_ITEM} as result. {ES_EWEASEL_RESULT_ANALYZER} will stop the loop.
 Just after pressed `start_test_run’ button, testing tool will try to find eweasel executable (e.g. eweasel.exe on Windows) under your $ISE_EIFFEL/eweasel/bin directory. If the executable not found, testing tool can’t not start the test run. And it will report error on the UI.

@@ Line 21: / Line 21: @@
 Eiffel Studio testing tool is a tool which launch eweasel executable in background.
 If launch success, eweasel output analyzers ({ES_EWEASEL_RESULT_ANALYZER}) will analyze all eweasel console outputs which redirected by process library. The {ES_EWEASEL_RESULT_ANALYZER} manage a set of {ES_EWEASEL_RESULT_HANDLER}s. The responsibility of {ES_EWEASEL_RESULT_ANALYZER} is try to find eweasel test run result output sections, and invoke all {ES_EWEASEL_RESULT_HANDLER} to handle the eweasel output. The eweasel result output section means the text block between two "Test " tags.
 {ES_EWEASEL_RESULT_HANDLER} is using chain of responsibility pattern. So different {ES_EWEASEL_RESULT_HANDLER} descandent will handle different eweasel output case. Such as {ES_EWEASEL_PASSED_RESULT_HANDLER} will try to find if there is ": passed" in a eweasel output section. If found, {ES_EWEASEL_PASSED_RESULT_HANDLER} will create a {ES_EWEASEL_TEST_RESULT_ITEM} as result. {ES_EWEASEL_RESULT_ANALYZER} will stop the loop.
 Just after pressed `start_test_run’ button, testing tool will try to find eweasel executable (e.g. eweasel.exe on Windows) under your $ISE_EIFFEL/eweasel/bin directory. If the executable not found, testing tool can’t not start the test run. And it will report error on the UI.
 == FAQ ==

@@ Line 22: / Line 22: @@
 Eiffel Studio testing tool is a tool which launch eweasel executable in background.
-If launch success, eweasel output analyzers will analyze all eweasel console outputs which redirected by process library.
+If launch success, eweasel output analyzers ({ES_EWEASEL_RESULT_ANALYZER}) will analyze all eweasel console outputs which redirected by process library. The {ES_EWEASEL_RESULT_ANALYZER} manage a set of {ES_EWEASEL_RESULT_HANDLER}s. The responsibility of {ES_EWEASEL_RESULT_ANALYZER} is try to find eweasel test run result output sections, and invoke all {ES_EWEASEL_RESULT_HANDLER} to handle the eweasel output. The eweasel result output section means the text block between two "Test " tags.
 Just after pressed `start_test_run’ button, testing tool will try to find eweasel executable (e.g. eweasel.exe on Windows) under your $ISE_EIFFEL/eweasel/bin directory. If the executable not found, testing tool can’t not start the test run. And it will report error on the UI.
 == FAQ ==

@@ Line 11: / Line 11: @@
 While creating test case files, {ES_NEW_EWEASEL_TEST_MANAGER} reads file templates from Eiffel Studio template directory ($ISE_EIFFEL/studio/help/defaults). The four template files are:
-eiffel_unit_test_class_template.e
+*eiffel_unit_test_class_template.e
-eiffel_unit_test_ecf_template.ecf
+*eiffel_unit_test_ecf_template.ecf
-eiffel_unit_test_note_template.txt
+*eiffel_unit_test_note_template.txt
-eiffel_unit_test_tcf_template.txt
+*eiffel_unit_test_tcf_template.txt
 After read template file, {ES_NEW_EWEASEL_TEST_MANAGER} will replace $SYMBOL in template files with generated texts (such as features under test, test case class name etc...). Finally, the files will be saved by {ES_NEW_EWEASEL_TEST_MANAGER} in the cluster selected by end user.

@@ Line 7: / Line 7: @@
 === Test case creation ===
-Testing tool can create unit test cases.
+Testing tool can create unit test cases. It depends on the test case creation wizard to get test case related information from end users. After end user gave all information, {ES_NEW_EWEASEL_TEST_MANAGER} will create a set of test case files which have four files (test case Eiffel class file, test case ecf file,	eweasel control file, tcf file, test case note file).
 === Test case execution ===

← Older revision		Revision as of 13:14, 22 April 2008
Line 2:		Line 2:

	This page explains how Eiffel Studio testing tool works under the hood. For Eiffel Studio testing tool general information, please see [[Eiffel_Testing_Tool]].		This page explains how Eiffel Studio testing tool works under the hood. For Eiffel Studio testing tool general information, please see [[Eiffel_Testing_Tool]].
		+
		+	== Main ideas ==
		+
		+	=== Test case creation ===
		+
		+	Testing tool can create unit test cases.
		+
		+	=== Test case execution ===
		+
		+	Eiffel Studio testing tool is a tool which launch eweasel executable in background.
		+
		+	If launch success, eweasel output analyzers will analyze all eweasel console outputs which redirected by process library.
		+
		+
		+	== Details ==
		+	Just after pressed `start_test_run’ button, testing tool will try to find eweasel executable (e.g. eweasel.exe on Windows) under your $ISE_EIFFEL/eweasel/bin directory. If the executable not found, testing tool can’t not start the test run. And it will report error on the UI.
		+
		+	== FAQ ==
		+
		+	=== If just after started testing, but eweasel is hanging ===
		+	This is normally caused by following three reasons:
		+
		+	*Precompiled lib version is not correct
		+	This normally happens just after you using a new version of ec.exe. So the precompiled library version mismatches. Please first precompiled the base and base-mt before use the testing tool.
		+
		+	*Your locale is not “en_US”.
		+	The solution is set ISE_LANG environment variable. “set ISE_LANG=en_US”
		+
		+	*ec compliant about $ISE_EIFFEL not exits just after started
		+	Please make sure your %ISE_EIFFEL environment is correct. Please make sure it isn’t end with “\” and the path exits.

← Older revision		Revision as of 09:20, 21 April 2008
Line 1:		Line 1:
		+	{{UnderConstruction}}
		+
	This page explains how Eiffel Studio testing tool works under the hood. For Eiffel Studio testing tool general information, please see [[Eiffel_Testing_Tool]].		This page explains how Eiffel Studio testing tool works under the hood. For Eiffel Studio testing tool general information, please see [[Eiffel_Testing_Tool]].