mirrors/eiffel-org
1
0
Fork 0
mirror of https://github.com/EiffelSoftware/eiffel-org.git synced 2025-12-07 07:12:25 +01:00
Code Issues Packages Projects Releases Wiki Activity

Author:halw

Browse Source 
Date:2009-02-23T15:04:25.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@194 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2009-02-23 15:04:25 +00:00
parent 813dc87e7e
commit ff832b67a7
3 changed files with 22 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/execute-tests.wiki
View File

@@ -103,7 +103,7 @@ This time we see that the test is successful, as indicated by the Success icon (
==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.
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.

2
documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/index.wiki
View File

@@ -10,7 +10,7 @@
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.
{{note|It is recommended, at least on your first viewing of this documentation, that you take the sections in the order in which they are presented. There are three different types of tests supported by the Eiffel Testing Framework. The topic of creation and use of each type of test occupies its own page. But to avoid repetition, the second and third pages omit some of the detail in the first and assume a familiarity with the example. }}
{{note|It is recommended, at least on your first viewing of this documentation, that you take the sections in the order in which they are presented. There are three different types of tests supported by the Eiffel Testing Framework. Each type of test is discussed on its own page. But to avoid repetition, the pages for the second and third types of tests omit some of the detail in the first and assume a familiarity with the example. }}

20
documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/managing-tests.wiki Normal file
View File

@@ -0,0 +1,20 @@
[[Property:title|Managing tests]]
[[Property:weight|9]]
[[Property:uuid|f1e7f63a-dc86-fefb-e669-3e3ea178c596]]
{{underconstruction}}
==Favoring manual tests==
==Deleting uneeded tests==
==Using Views and Filters==