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

Author:halw

Browse Source 
Date:2009-02-16T22:56:08.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@185 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2009-02-16 22:56:08 +00:00
parent b7b8bcf3eb
commit f81575795b
2 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -1,6 +1,10 @@
[[Property:title|Execute tests]]
[[Property:weight|3]]
[[Property:uuid|d0515cb1-0792-3028-2a24-a71b56506959]]
{{underconstruction}}
In the previous section we coded a manually created test. The Eiffel Testing Framework will allow us to execute that test, or, in more practical terms, any set of tests that we select. But before we execute our test, let's take a look at what we will get out of such an execution.
==About Test Results==
@@ -51,6 +55,8 @@ You see that the "Status" of <code>test_deposit</code> is "not tested", and that
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.
==Examining test results==
The test runs in background and the Eiffel Testing Framework interface now looks like this:

2
documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/testing-background-and-basics.wiki
View File

@@ -79,7 +79,7 @@ Manual tests are features, procedures in fact, of classes that inherit from EQA_
A manual test is "manual" in the sense that you code the essential procedural part of the test by hand. But you really don't have to deal with the more mundane business of creating the whole test class and ensuring the proper inheritance. The ''New Eiffel Test Wizard'' helps out by automatically creating the shell of a test class and the shell of a test for you to fill in. Then it's pretty easy to add new tests manually to an existing test class.
{{definition|Synthesized test|A test that is the product of generating and running a series of randomly generated invocations target routines. }}
{{definition|Synthesized test|A test that is the product of generating and running a series of randomly generated invocations of target routines. }}
The process of creating synthesized tests is sometimes known in the community as creating via ''AutoTest''. The randomly generated calls to target routines which were created and run are discarded at the completion of the creation. But from the results of these calls, a set of permanent tests is distilled. These are the synthesized tests.