mirror of
https://github.com/EiffelSoftware/eiffel-org.git
synced 2025-12-06 14:52:03 +01:00
Author:halw
Date:2009-02-17T21:28:07.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@186 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
@@ -101,10 +101,15 @@ After compiling, we execute the test again, and view the result:
|
||||
|
||||
This time we see that the test is successful, as indicated by the Success icon ( [[Image:general-tick-icon]] ) in the Status column.
|
||||
|
||||
==The start of a test suite==
|
||||
==The beginnings of a test suite==
|
||||
|
||||
Of course, we would not have had to use the Eiffel Testing Framework to find that bug in <code>{BANK_ACCOUNT}.deposit</code>. We could have just written a simple class to exercise instances of <code>BANK_ACCOUNT</code> and truth would have come out.
|
||||
|
||||
The advantage of using the Eiffel Testing Framework is that the test that we wrote to cover <code>{BANK_ACCOUNT}.deposit</code> can stay with us throughout the lifecycle of class <code>BANK_ACCOUNT</code>. We can expand the <code>TEST_BANK_ACCOUNT</code> with additional manual tests and run them after every development increment to ensure that all tests that were once successful are still successful.
|
||||
|
||||
==Manual test summary==
|
||||
|
||||
We have seen how to create and execute a manual test. You will find that manual tests form the backbone of your test suite. But there are two other times of tests available in the Eiffel Testing Framework. Next let's take a look at these test types and in what ways they can be used.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@
|
||||
|
||||
==Overview==
|
||||
|
||||
The Eiffel Testing Framework is a tool that helps you to create, manage, and run tests against your software. The Eiffel Testing Framework is accessible directly as a part of EiffelStudio, but works to a large extent behind the scenes so that it doesn't get in the way of your development activities. In other words, even though you may be accumulating a substantial collection of test software along with your project software, you can still run and deliver your project software without going to a lot of trouble separating the two. Tests managed by the Eiffel Testing Framework stay handy and can be run any time to help make sure everything still stands up to the scrutiny of testing.
|
||||
The Eiffel Testing Framework is a tool that helps you to create, manage, and run tests against your software. The Eiffel Testing Framework is accessible directly as a part of EiffelStudio, but works to a large extent behind the scenes so that it doesn't get in the way of your development activities. In other words, even though you may be accumulating a substantial collection of test software along with your project software, you can still run and deliver your project software without going to a lot of trouble separating the two. Tests managed by the Eiffel Testing Framework stay handy and can be run any time to help make sure everything always stands up to the scrutiny of testing.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -95,6 +95,7 @@ Extracted tests are convenient because they allow you to accumulate tests that a
|
||||
|
||||
==Anatomy of a test==
|
||||
|
||||
Here are two more definitions:
|
||||
|
||||
{{definition|Target routine|A routine that is to be tested by a test. Sometimes called a "routine under test." }}
|
||||
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
[[Property:title|Using extracted tests]]
|
||||
[[Property:weight|5]]
|
||||
[[Property:uuid|bebd4f28-9818-80f0-a69a-e9ce867723f4]]
|
||||
{{underconstruction}}
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -0,0 +1,11 @@
|
||||
[[Property:title|Using synthesized tests]]
|
||||
[[Property:link_title|Using generated tests]]
|
||||
[[Property:weight|7]]
|
||||
[[Property:uuid|c17ebddf-5d35-76c1-4912-d9f1ca3770a5]]
|
||||
|
||||
{{underconstruction}}
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user