mirrors/eiffel-org
1
0
Fork 0
mirror of https://github.com/EiffelSoftware/eiffel-org.git synced 2026-04-05 09:39:31 +02:00
Code Issues Packages Projects Releases Wiki Activity

Author:halw

Browse Source 
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:
halw
2009-02-17 21:28:07 +00:00
parent f81575795b
commit fa0b1e7577
5 changed files with 28 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -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.