Eweasel Integration - Revision history

Larryl: /* How it works */

2008-09-12T10:17:03Z

How it works

Larryl: /* Main ideas and main classes */

2008-09-12T10:14:03Z

Main ideas and main classes

← Older revision		Revision as of 10:14, 12 September 2008
Line 6:		Line 6:
	== Main ideas and main classes ==		== Main ideas and main classes ==

	The main idea is using normal Eiffel classes to replace ~~orignal~~ Eweasel testing control/catalog files. It means, in 6.3, we will write Eweasel testing control/catalog files in normal Eiffel classes instead of ~~writting~~ the eweasel instructions in plain text files.		The main idea is using normal Eiffel classes to replace original Eweasel testing control/catalog files. It means, in 6.3, we will write Eweasel testing control/catalog files in normal Eiffel classes instead of writing the eweasel instructions in plain text files.

	=== First, what testing control file looks like in 6.3 ===		=== First, what testing control file looks like in 6.3 ===
Line 156:		Line 156:
	</eiffel>		</eiffel>

	The feature `start_test_sample' replaced ~~orignal~~ `eweasel' executable command line. For example, on Windows, the command line is:		The feature `start_test_sample' replaced original `eweasel' executable command line. For example, on Windows, the command line is:

	eweasel.exe -init c:\eweasel\control\init -output c:\test_output -define ISE_EIFFEL c:\PROGRA~1\EIFFEL~1\EIFFEL~1.3GP -define		eweasel.exe -init c:\eweasel\control\init -output c:\test_output -define ISE_EIFFEL c:\PROGRA~1\EIFFEL~1\EIFFEL~1.3GP -define

Larryl: /* Classes will not seen by end users */

2008-09-12T10:00:09Z

Classes will not seen by end users

← Older revision		Revision as of 10:00, 12 September 2008
Line 189:		Line 189:

	{EW_TEST_INST} which inherit old {TEST_INST}		{EW_TEST_INST} which inherit old {TEST_INST}

			Because old eweasel rely on plain text files to have testing instructions, but the new 6.3 eweasel will using normal Eiffel classes directly. These classes are mainly adapte this issue, so the 6.3 eweasel can work.

	== Testing control file converter ==		== Testing control file converter ==

	Tha main idea of the testing control file converter is: parsing old testing control/catalog files then generate Eiffel classes files which can be used by the new eweasel 6.3.		Tha main idea of the testing control file converter is: parsing old testing control/catalog files then generate Eiffel classes files which can be used by the new eweasel 6.3.

Larryl: /* Third, how to start Eweasel testing in 6.3 */

2008-09-12T09:52:31Z

Third, how to start Eweasel testing in 6.3

← Older revision		Revision as of 09:52, 12 September 2008
Line 123:		Line 123:
	-- Start eweasel testing		-- Start eweasel testing
	local		local
	l_eweasel_63: ~~EWEASEL_63~~		l_eweasel_63: EW_EWEASEL_MT
	l_list: ARRAYED_LIST [EW_TEST_CATALOG_INSTRUCTIONS]		l_list: ARRAYED_LIST [EW_TEST_CATALOG_INSTRUCTIONS]
	l_catalog_adapter: EWEASEL_TEST_CATALOG_SAMPLE		l_catalog_adapter: EWEASEL_TEST_CATALOG_SAMPLE
Line 130:		Line 130:

	l_eweasel_63.init ("c:\eweasel\control\init")		l_eweasel_63.init ("c:\eweasel\control\init")
	l_eweasel_63.~~output_argu~~ ("c:\test_output")		l_eweasel_63.output_arg ("c:\test_output")
	l_eweasel_63.define ("ISE_EIFFEL", "c:\PROGRA~1\EIFFEL~1\EIFFEL~1.3GP")		l_eweasel_63.define ("ISE_EIFFEL", "c:\PROGRA~1\EIFFEL~1\EIFFEL~1.3GP")
	l_eweasel_63.define ("ISE_PLATFORM", "windows")		l_eweasel_63.define ("ISE_PLATFORM", "windows")

Larryl: /* {EW_EWEASEL_MT} = */

2008-09-12T09:51:46Z

{EW_EWEASEL_MT} =

← Older revision		Revision as of 09:51, 12 September 2008
Line 178:		Line 178:
	The catalog instruction feature will prepare a correspond {CATALOG_INSTRUCTION} descdant. Then it will execute (call {CATALOG_INSTRUCTION}.execute) the catalog instruction immediately just like what old eweasel does in {TEST_CATALOG_FILE}.parse_line.		The catalog instruction feature will prepare a correspond {CATALOG_INSTRUCTION} descdant. Then it will execute (call {CATALOG_INSTRUCTION}.execute) the catalog instruction immediately just like what old eweasel does in {TEST_CATALOG_FILE}.parse_line.

	== {EW_EWEASEL_MT} ===		=== {EW_EWEASEL_MT} ===

	The propose of {EW_EWEASEL_MT} is staring eweasel testing and letting end users specifing various parameters, such as: define, keep_all, clean, init, catalog, output_arg...		The propose of {EW_EWEASEL_MT} is staring eweasel testing and letting end users specifing various parameters, such as: define, keep_all, clean, init, catalog, output_arg...

Larryl: /* How it works */

2008-09-12T09:51:28Z

How it works

← Older revision		Revision as of 09:51, 12 September 2008
Line 177:		Line 177:

	The catalog instruction feature will prepare a correspond {CATALOG_INSTRUCTION} descdant. Then it will execute (call {CATALOG_INSTRUCTION}.execute) the catalog instruction immediately just like what old eweasel does in {TEST_CATALOG_FILE}.parse_line.		The catalog instruction feature will prepare a correspond {CATALOG_INSTRUCTION} descdant. Then it will execute (call {CATALOG_INSTRUCTION}.execute) the catalog instruction immediately just like what old eweasel does in {TEST_CATALOG_FILE}.parse_line.

			== {EW_EWEASEL_MT} ===

			The propose of {EW_EWEASEL_MT} is staring eweasel testing and letting end users specifing various parameters, such as: define, keep_all, clean, init, catalog, output_arg...

	=== Classes will not seen by end users ===		=== Classes will not seen by end users ===

Larryl: /* How it works */

2008-09-12T09:44:56Z

How it works

← Older revision		Revision as of 09:44, 12 September 2008
Line 164:		Line 164:
	== How it works ==		== How it works ==

	Acutally, most of eweasel integration classes work as adapters.		Acutally most of eweasel integration classes work as adapters.

	=== {EW_TEST_CONTROL_INSTRUCTIONS} ===		=== {EW_TEST_CONTROL_INSTRUCTIONS} ===

Larryl: /* How it works */

2008-09-12T09:44:29Z

How it works

← Older revision		Revision as of 09:44, 12 September 2008
Line 177:		Line 177:

	The catalog instruction feature will prepare a correspond {CATALOG_INSTRUCTION} descdant. Then it will execute (call {CATALOG_INSTRUCTION}.execute) the catalog instruction immediately just like what old eweasel does in {TEST_CATALOG_FILE}.parse_line.		The catalog instruction feature will prepare a correspond {CATALOG_INSTRUCTION} descdant. Then it will execute (call {CATALOG_INSTRUCTION}.execute) the catalog instruction immediately just like what old eweasel does in {TEST_CATALOG_FILE}.parse_line.

			=== Classes will not seen by end users ===

			{EW_TEST_CONTROL_FILE} which inherit old {TEST_CONTROL_FILE}

			{EW_TEST_CATALOG_FILE} which inherit old {TEST_CATALOG_FILE}

			{EW_TEST_INST} which inherit old {TEST_INST}

	== Testing control file converter ==		== Testing control file converter ==

	Tha main idea of the testing control file converter is: parsing old testing control/catalog files then generate Eiffel classes files which can be used by the new eweasel 6.3.		Tha main idea of the testing control file converter is: parsing old testing control/catalog files then generate Eiffel classes files which can be used by the new eweasel 6.3.

Larryl: /* Testing control file converter */

2008-09-12T09:33:39Z

Testing control file converter

← Older revision		Revision as of 09:33, 12 September 2008
Line 179:		Line 179:

	== Testing control file converter ==		== Testing control file converter ==

			Tha main idea of the testing control file converter is: parsing old testing control/catalog files then generate Eiffel classes files which can be used by the new eweasel 6.3.

Larryl: /* {EW_TEST_CATALOG_INSTRUCTIONS} */

2008-09-12T09:31:49Z

{EW_TEST_CATALOG_INSTRUCTIONS}

← Older revision		Revision as of 09:31, 12 September 2008
Line 174:		Line 174:
	=== {EW_TEST_CATALOG_INSTRUCTIONS} ===		=== {EW_TEST_CATALOG_INSTRUCTIONS} ===

	Similar to {EW_TEST_CONTROL_INSTRUCTIONS}, end users should inherit class {EW_TEST_CATALOG_INSTRUCTIONS} to write new eweasel testing catalog file. The {EW_TEST_CATALOG_INSTRUCTIONS} have all the testing catalog instructions which old eweasel has.		Similar to {EW_TEST_CONTROL_INSTRUCTIONS}, end users should inherit class {EW_TEST_CATALOG_INSTRUCTIONS} to write new eweasel testing catalog file. The {EW_TEST_CATALOG_INSTRUCTIONS} have all the testing catalog instructions which old eweasel has. The three instruction features in this class are catalog_if (orignal name is `if'), source_path and test.

			The catalog instruction feature will prepare a correspond {CATALOG_INSTRUCTION} descdant. Then it will execute (call {CATALOG_INSTRUCTION}.execute) the catalog instruction immediately just like what old eweasel does in {TEST_CATALOG_FILE}.parse_line.

	== Testing control file converter ==		== Testing control file converter ==

← Older revision		Revision as of 10:17, 12 September 2008
Line 164:		Line 164:
	== How it works ==		== How it works ==

	~~Acutally~~ most of eweasel integration classes work as adapters.		Actually most of eweasel integration classes work as adapters.

	=== {EW_TEST_CONTROL_INSTRUCTIONS} ===		=== {EW_TEST_CONTROL_INSTRUCTIONS} ===
Line 174:		Line 174:
	=== {EW_TEST_CATALOG_INSTRUCTIONS} ===		=== {EW_TEST_CATALOG_INSTRUCTIONS} ===

	Similar to {EW_TEST_CONTROL_INSTRUCTIONS}, end users should inherit class {EW_TEST_CATALOG_INSTRUCTIONS} to write new eweasel testing catalog file. The {EW_TEST_CATALOG_INSTRUCTIONS} have all the testing catalog instructions which old eweasel has. The three instruction features in this class are catalog_if (~~orignal~~ name is `if'), source_path and test.		Similar to {EW_TEST_CONTROL_INSTRUCTIONS}, end users should inherit class {EW_TEST_CATALOG_INSTRUCTIONS} to write new eweasel testing catalog file. The {EW_TEST_CATALOG_INSTRUCTIONS} have all the testing catalog instructions which old eweasel has. The three instruction features in this class are catalog_if (original name is `if'), source_path and test.

	The catalog instruction feature will prepare a correspond {CATALOG_INSTRUCTION} ~~descdant~~. Then it will execute (call {CATALOG_INSTRUCTION}.execute) the catalog instruction immediately just like what old eweasel does in {TEST_CATALOG_FILE}.parse_line.		The catalog instruction feature will prepare a correspond {CATALOG_INSTRUCTION} descendant. Then it will execute (call {CATALOG_INSTRUCTION}.execute) the catalog instruction immediately just like what old eweasel does in {TEST_CATALOG_FILE}.parse_line.

	=== {EW_EWEASEL_MT} ===		=== {EW_EWEASEL_MT} ===

	The propose of {EW_EWEASEL_MT} is staring eweasel testing and letting end users ~~specifing~~ various parameters, such as: define, keep_all, clean, init, catalog, output_arg...		The propose of {EW_EWEASEL_MT} is staring eweasel testing and letting end users specifying various parameters, such as: define, keep_all, clean, init, catalog, output_arg...

	=== Classes will not seen by end users ===		=== Classes will not seen by end users ===
Line 190:		Line 190:
	{EW_TEST_INST} which inherit old {TEST_INST}		{EW_TEST_INST} which inherit old {TEST_INST}

	Because old eweasel rely on plain text files to have testing instructions, but the new 6.3 eweasel will using normal Eiffel classes directly. These classes are mainly ~~adapte~~ this issue, so the 6.3 eweasel can work.		Because old eweasel rely on plain text files to have testing instructions, but the new 6.3 eweasel will using normal Eiffel classes directly. These classes are mainly adapt this issue, so the 6.3 eweasel can work.

	== Testing control file converter ==		== Testing control file converter ==

	Tha main idea of the testing control file converter is: parsing old testing control/catalog files then generate Eiffel classes files which can be used by the new eweasel 6.3.		Tha main idea of the testing control file converter is: parsing old testing control/catalog files then generate Eiffel classes files which can be used by the new eweasel 6.3.