Eiffeltest - Revision history

Hzwakenberg at 13:01, 9 September 2018

2018-09-09T13:01:32Z

← Older revision		Revision as of 15:01, 9 September 2018
Line 4:		Line 4:
	Users can use it to run a test-suite of their own, which is a useful tool for their project robustness.		Users can use it to run a test-suite of their own, which is a useful tool for their project robustness.

−	It is also used by the Liberty Eiffel development team itself to validate~~, with~~ the ~~provided~~ ~~test-suite,~~ the ~~compiler~~ ~~and~~ the ~~libraries~~.	+	It is also used by the Liberty Eiffel development team itself to validate the compiler and the libraries, using the provided test-suite.

	== Synopsis ==		== Synopsis ==

Hzwakenberg at 13:00, 9 September 2018

2018-09-09T13:00:04Z

← Older revision		Revision as of 15:00, 9 September 2018
Line 4:		Line 4:
	Users can use it to run a test-suite of their own, which is a useful tool for their project robustness.		Users can use it to run a test-suite of their own, which is a useful tool for their project robustness.

−	It is also used by the Liberty Eiffel team itself to validate, with the provided test-suite, the compiler and the libraries.	+	It is also used by the Liberty Eiffel development team itself to validate, with the provided test-suite, the compiler and the libraries.

	== Synopsis ==		== Synopsis ==

Hzwakenberg at 12:57, 9 September 2018

2018-09-09T12:57:36Z

← Older revision		Revision as of 14:57, 9 September 2018
Line 4:		Line 4:
	Users can use it to run a test-suite of their own, which is a useful tool for their project robustness.		Users can use it to run a test-suite of their own, which is a useful tool for their project robustness.

−	It is also used by Liberty Eiffel itself to validate, with the provided test-suite, the compiler and the libraries.	+	It is also used by the Liberty Eiffel team itself to validate, with the provided test-suite, the compiler and the libraries.

	== Synopsis ==		== Synopsis ==
Line 12:		Line 12:
	== File handling ==		== File handling ==

−	The tools recursively ~~iterates~~ over the directory given as a command-line parameter, looking for test files or over the given test file names.	+	The tools recursively iterate over the directory given as a command-line parameter, looking for test files or over the given test file names.

	Test files are Eiffel source files with special names:		Test files are Eiffel source files with special names:

Hzwakenberg at 07:35, 17 June 2016

2016-06-17T07:35:03Z

← Older revision		Revision as of 09:35, 17 June 2016
Line 4:		Line 4:
	Users can use it to run a test-suite of their own, which is a useful tool for their project robustness.		Users can use it to run a test-suite of their own, which is a useful tool for their project robustness.

−	It is also used by ~~LibertyEiffel~~ itself to validate, with the provided test-suite, the compiler and the libraries.	+	It is also used by Liberty Eiffel itself to validate, with the provided test-suite, the compiler and the libraries.

	== Synopsis ==		== Synopsis ==

Ramack: /* Synopsis */

2016-05-22T11:24:56Z

Synopsis

← Older revision		Revision as of 13:24, 22 May 2016
Line 9:		Line 9:

	* <code>se test directory </code>		* <code>se test directory </code>
−
−	* <code>se test source_file.e [source_file2.e...] </code>

	== File handling ==		== File handling ==

Ramack: move open point, add test implementation

2016-04-08T18:47:26Z

move open point, add test implementation

@@ Line 33: / Line 33: @@
 In each test directory a file named loadpath.se may exist, which is passed to the compiler as loadpath.
 == Modes that are checked ==
@@ Line 164: / Line 176: @@
 ''Nice idea. I would improve it by proposing the opposite: list the modes/options to exclude. This means that all modes will be checked by default. If the test is incompatible with some mode, then it has to be specified. If some new mode is added, this mode will be tested with all tests. If some tests are not compatible with this mode, they have to be excluded. Otherway, you would have to edit about every test to add this mode. -- Philippe Ribet

Ramack: /* Modes that are checked */ adjusted, bust might still be inconsistent. See feature test_list_check in http://git.savannah.gnu.org/cgit/liberty-eiffel.git/tree/src/smarteiffel/commands/eiffeltest.e

2015-09-21T19:40:28Z

Modes that are checked: adjusted, bust might still be inconsistent. See feature test_list_check in http://git.savannah.gnu.org/cgit/liberty-eiffel.git/tree/src/smarteiffel/commands/eiffeltest.e

← Older revision		Revision as of 21:40, 21 September 2015
Line 47:		Line 47:
	\|-		\|-
	\|		\|
−	* -boost	+	* -boost
		+	* -boost -bdw_gc
−	* -flat_check -debug_check
		+	* -boost -debug -bdw_gc
	* -no_check		* -no_check
		+	* -no_check -bdw_gc
		+	\|
		+	* -flat_check -all_check -debug
	* -flat_check -require_check		* -flat_check -require_check
	* -flat_check -ensure_check		* -flat_check -ensure_check
Line 55:		Line 59:
	* -flat_check -loop_check		* -flat_check -loop_check
	* -flat_check -all_check		* -flat_check -all_check
		+	\|
		+	* -flat_check -no_check -bdw_gc
		+	* -flat_check -require_check -bdw_gc
		+	* -flat_check -ensure_check -bdw_gc
		+	* -flat_check -invariant_check -bdw_gc
		+	* -flat_check -loop_check -bdw_gc
		+	* -flat_check -all_check -bdw_gc
	\|		\|
	* -no_gc -boost		* -no_gc -boost
−	* -no_gc -~~flat_check~~ -~~debug_check~~	+	* -no_gc -boost -debug
	* -no_gc -no_check		* -no_gc -no_check
	* -no_gc -flat_check -require_check		* -no_gc -flat_check -require_check
	* -no_gc -ensure_check		* -no_gc -ensure_check
		+	\|-
		+	\|
		+	* -no_gc -flat_check -debug
	* -no_gc -flat_check -invariant_check		* -no_gc -flat_check -invariant_check
	* -no_gc -flat_check -loop_check		* -no_gc -flat_check -loop_check
	* -no_gc -flat_check -all_check		* -no_gc -flat_check -all_check
	\|		\|
		+	* -all_check -debug
−	* -debug_check
	* -require_check		* -require_check
	* -ensure_check		* -ensure_check
Line 71:		Line 85:
	* -loop_check		* -loop_check
	* -all_check		* -all_check
		+	* -debug
	\|		\|
−	* -no_gc -~~debug_check~~	+	* -no_gc -all_check -debug
	* -no_gc -require_check		* -no_gc -require_check
	* -no_gc -ensure_check		* -no_gc -ensure_check
Line 78:		Line 93:
	* -no_gc -loop_check		* -no_gc -loop_check
	* -no_gc -all_check		* -no_gc -all_check
		+	\|
		+	* -all_check -debug -bdw_gc
		+	* -require_check -bdw_gc
		+	* -ensure_check -bdw_gc
		+	* -invariant_check -bdw_gc
		+	* -loop_check -bdw_gc
		+	* -all_check -bdw_gc
		+	* -debug -bdw_gc
	\|-		\|-
	\|		\|
	* -profile -boost		* -profile -boost
−	* -profile -~~debug_check~~	+	* -profile -all_check -debug
	* -profile -no_check		* -profile -no_check
	* -profile -require_check		* -profile -require_check
Line 90:		Line 113:
	\|		\|
	* -profile -no_gc -boost		* -profile -no_gc -boost
−	* -profile -no_gc -~~debug_check~~	+	* -profile -no_gc -all_check -debug
	* -profile -no_gc -no_check		* -profile -no_gc -no_check
	* -profile -no_gc -require_check		* -profile -no_gc -require_check
Line 98:		Line 121:
	* -profile -no_gc -all_check		* -profile -no_gc -all_check
	\|		\|
−	* -profile -~~flat_check~~ -~~debug_check~~	+	* -profile -boost -bwd_gc
		+	* -profile -all_check -debug -bdw_gc
		+	* -profile -no_check -bdw_gc
		+	* -profile -require_check -bdw_gc
		+	* -profile -ensure_check -bdw_gc
		+	* -profile -invariant_check -bdw_gc
		+	* -profile -loop_check -bdw_gc
		+	* -profile -all_check -bdw_gc
		+	\|
		+	* -profile -flat_check -all_check -debug
	* -profile -flat_check -require_check		* -profile -flat_check -require_check
	* -profile -flat_check -ensure_check		* -profile -flat_check -ensure_check
Line 104:		Line 136:
	* -profile -flat_check -loop_check		* -profile -flat_check -loop_check
	* -profile -flat_check -all_check		* -profile -flat_check -all_check
		+	\|-
	\|		\|
	* -no_split -boost		* -no_split -boost
	* -no_split -no_gc -boost		* -no_split -no_gc -boost
		+	* -no_split -boost -bdw_gc
	\|}		\|}
−

	== Open issues ==		== Open issues ==

Hzwakenberg at 18:31, 7 September 2014

2014-09-07T18:31:38Z

← Older revision		Revision as of 20:31, 7 September 2014
Line 1:		Line 1:
		+	[[Category: Tool]]
	<code>eiffeltest</code> is a tool that runs a suite of tests.		<code>eiffeltest</code> is a tool that runs a suite of tests.

Hzwakenberg at 19:42, 5 September 2014

2014-09-05T19:42:45Z

← Older revision		Revision as of 21:42, 5 September 2014
Line 1:		Line 1:
−	[[Category:Smarteiffel]]
−
−	This page specifies a tool that is currently being written.
−	Check the [http://gforge.inria.fr/plugins/scmsvn/viewcvs.php/trunk/?root=smarteiffel Subversion repository] if you want premium access to the tool.
−
	<code>eiffeltest</code> is a tool that runs a suite of tests.		<code>eiffeltest</code> is a tool that runs a suite of tests.

	Users can use it to run a test-suite of their own, which is a useful tool for their project robustness.		Users can use it to run a test-suite of their own, which is a useful tool for their project robustness.

−	It is also used by ~~SmartEiffel~~ itself to validate, with the provided test-suite, the compiler and the libraries.	+	It is also used by LibertyEiffel itself to validate, with the provided test-suite, the compiler and the libraries.

	== Synopsis ==		== Synopsis ==

Ramack at 21:10, 4 March 2013

2013-03-04T21:10:07Z

← Older revision		Revision as of 23:10, 4 March 2013
Line 1:		Line 1:
−	[[Category: ~~Book~~]]	+	[[Category:Smarteiffel]]

	This page specifies a tool that is currently being written.		This page specifies a tool that is currently being written.