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-25T15:28:38.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@197 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2009-02-25 15:28:38 +00:00
parent 56ffb8b753
commit c3aa41677c
4 changed files with 21 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -51,7 +51,7 @@ Here you see under "Tests" the project cluster <code>bank_account</code>, the te
{{note|If you've been working along in EiffelStudio, and you don't see this display, then go to the View combo box and type in "class" as shown in the pane above and press enter. Later we will see more about using the View and Filter boxes. }}
You see that the "Status" of <code>test_deposit</code> is "not tested", and that the "Last executed" date is empty.
You see that the '''Status''' of <code>test_deposit</code> is "not tested", and that the '''Last executed''' date is empty.
To execute tests we use the "Run" button ( [[Image:debug-run-icon]] ) on the interface toolbar. The Run button will run all tests by default. However, there is a list of run options that you can access by clicking the black triangle just to the right of Run. You can choose to run all tests, only those with failing status, a filtered set of tests, or only those tests that you have selected in the tree below. We'll cover filtering a little later. For now, life is simple, we have only one test so just clicking the Run button should execute it.
@@ -63,7 +63,7 @@ The test runs in background and the Eiffel Testing Framework interface now looks
[[Image:Testing Framework interface after run 01]]
It's pretty clear that our test has failed. Its status is now marked with the Failing icon ( [[Image:general-error-icon]] ) and in the box below the "Execution" tab we see that the status also includes a tag: <code>balance_increased</code>. To get a more detailed analysis, we can double-click the test in the "Tests" box.
It's pretty clear that our test has failed. Its status is now marked with the Failing icon ( [[Image:general-error-icon]] ) and in the box below the '''Execution''' tab we see that the status also includes a tag: <code>balance_increased</code>. To get a more detailed analysis, we can double-click the test in the '''Tests''' box.
[[Image:Testing Framework interface after run 02]]