Category:Testing - Revision history

Bertrand Meyer at 22:33, 8 August 2007

2007-08-08T22:33:53Z

2007-08-08T22:33:38Z

2007-08-08T22:33:06Z

2007-05-30T18:23:18Z

2007-05-30T18:22:40Z

2007-05-30T18:22:12Z

2007-05-30T18:11:45Z

2007-05-30T17:55:56Z

2007-05-30T17:55:28Z

2006-04-04T05:09:24Z

New page

Pages related to testing of compiler, EiffelStudio and libraries.

@@ Line 1: / Line 1: @@
 [[Category:Projects]]
-{{NoProjectMemberd}}
+{{NoProjectMembers}}
 A systematic testing process is necessary to produce a timely release with a high level of quality. The last six weeks of a release cycle are entirely devoted to testing. The general organization is described below.

@@ Line 1: / Line 1: @@
-[Category:Projects]
+[[Category:Projects]]
-{{NoProjectsMember}}
+{{NoProjectMemberd}}
 A systematic testing process is necessary to produce a timely release with a high level of quality. The last six weeks of a release cycle are entirely devoted to testing. The general organization is described below.

← Older revision		Revision as of 22:33, 8 August 2007
Line 1:		Line 1:
		+	[Category:Projects]
		+	{{NoProjectsMember}}
		+
	A systematic testing process is necessary to produce a timely release with a high level of quality. The last six weeks of a release cycle are entirely devoted to testing. The general organization is described below.		A systematic testing process is necessary to produce a timely release with a high level of quality. The last six weeks of a release cycle are entirely devoted to testing. The general organization is described below.

← Older revision		Revision as of 18:23, 30 May 2007
Line 7:		Line 7:

	For the compiler, we use the '''[[Eweasel]]''' regression testing tool. It consists of a set of systems that are compiled. The tool checks for each system that an error is reported if one should, or that no error occurs if none are expected. It also checks that executing a system yield the right execution semantics.		For the compiler, we use the '''[[Eweasel]]''' regression testing tool. It consists of a set of systems that are compiled. The tool checks for each system that an error is reported if one should, or that no error occurs if none are expected. It also checks that executing a system yield the right execution semantics.
		+
		+	You will find below various links to all the testing tools and formalisms we use to accomplish our testing.

← Older revision		Revision as of 18:22, 30 May 2007
Line 6:		Line 6:
	*The testing process consists of running these test scenarios; the result of any such run is a [http://eiffelsoftware.origo.ethz.ch/testing/ '''Test Run Report (TRR)'''].		*The testing process consists of running these test scenarios; the result of any such run is a [http://eiffelsoftware.origo.ethz.ch/testing/ '''Test Run Report (TRR)'''].

−	For the compiler, we use the [[Eweasel]] regression testing tool. It consists of a set of systems that are compiled. The tool checks for each system that an error is reported if one should, or that no error occurs if none are expected. It also checks that executing a system yield the right execution semantics.	+	For the compiler, we use the '''[[Eweasel]]''' regression testing tool. It consists of a set of systems that are compiled. The tool checks for each system that an error is reported if one should, or that no error occurs if none are expected. It also checks that executing a system yield the right execution semantics.

← Older revision		Revision as of 18:11, 30 May 2007
Line 5:		Line 5:
	*The test plan is made of a number of descriptions of tests to be run, each known as a [http://eiffelsoftware.origo.ethz.ch/testing/tcs/ '''Test Case Specifications (TCS)''']. A TCS specifies a test scenario; it is not related to any particular execution of that scenario.		*The test plan is made of a number of descriptions of tests to be run, each known as a [http://eiffelsoftware.origo.ethz.ch/testing/tcs/ '''Test Case Specifications (TCS)''']. A TCS specifies a test scenario; it is not related to any particular execution of that scenario.
	*The testing process consists of running these test scenarios; the result of any such run is a [http://eiffelsoftware.origo.ethz.ch/testing/ '''Test Run Report (TRR)'''].		*The testing process consists of running these test scenarios; the result of any such run is a [http://eiffelsoftware.origo.ethz.ch/testing/ '''Test Run Report (TRR)'''].
		+
		+	For the compiler, we use the [[Eweasel]] regression testing tool. It consists of a set of systems that are compiled. The tool checks for each system that an error is reported if one should, or that no error occurs if be reported, and it also checks that executing a system yield the right execution semantics.

@@ Line 1: / Line 1: @@
-=Overview=
+A systematic testing process is necessary to produce a timely release with a high level of quality. The last six weeks of a release cycle are entirely devoted to testing. The general organization is described below.
-−
-A systematic testing process is necessary to produce a timely release with a high level of quality. The last six weeks of the release cycle are entirely devoted to testing. The general organization is described below.
 At this level of the development all testing is performed by a team member '''other''' than the developer of the corresponding system or subsystem. The testing process is formalized:

← Older revision		Revision as of 17:55, 30 May 2007
Line 1:		Line 1:
−	~~Pages related~~ to testing of ~~compiler, EiffelStudio~~ and ~~libraries~~.	+	=Overview=
		+
		+	A systematic testing process is necessary to produce a timely release with a high level of quality. The last six weeks of the release cycle are entirely devoted to testing. The general organization is described below.
		+
		+	At this level of the development all testing is performed by a team member '''other''' than the developer of the corresponding system or subsystem. The testing process is formalized:
		+	*For each system and subsystem, a [http://eiffelsoftware.origo.ethz.ch/testing/plan/ '''Test Plan'''] is created accordingly.
		+	*The test plan is made of a number of descriptions of tests to be run, each known as a [http://eiffelsoftware.origo.ethz.ch/testing/tcs/ '''Test Case Specifications (TCS)''']. A TCS specifies a test scenario; it is not related to any particular execution of that scenario.
		+	*The testing process consists of running these test scenarios; the result of any such run is a [http://eiffelsoftware.origo.ethz.ch/testing/ '''Test Run Report (TRR)'''].