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-05-24T19:13:31.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@226 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2009-05-24 19:13:31 +00:00
parent 9acf7bb62d
commit e3afbd3f8c
10 changed files with 37 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/create-manual-test.wiki
View File

@@ -1,8 +1,6 @@
[[Property:title|Create a manual test]]
[[Property:weight|2]]
[[Property:uuid|e78f25e3-ed3a-f8fa-e71d-28a4dda1825f]]
{{underconstruction}}
==A system to test==

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

@@ -1,8 +1,6 @@
[[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.

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

@@ -1,9 +1,6 @@
[[Property:title|Managing tests]]
[[Property:weight|9]]
[[Property:uuid|f1e7f63a-dc86-fefb-e669-3e3ea178c596]]
{{underconstruction}}
The previous sections cover the basics of testing and what it takes to create and use each of the test types supported by the Eiffel Testing Framework. This section will finish things up with some miscellaneous information about testing strategy and hints on using of the Framework.
@@ -28,6 +25,9 @@ If you want to remove a whole test set, then [[Removing a class|delete the class
==Using Views and Filters==
{{note|The development of this documentation section is currently on hold pending changes to the interface expected in an upcoming release. }}
Views and Filters are provided to help view, manage, and run the tests in a test suite.
Views control ''how'' the view of tests is organized in the Eiffel Testing Framework interface. You can display tests organized by the test classes that contain them, by the classes they target, by their type, by their most recent results, or by any system you set up using a system of [[Create a manual test#About tags|tags]].

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

@@ -1,8 +1,6 @@
[[Property:title|Testing: Background and basics]]
[[Property:weight|0]]
[[Property:uuid|12c2a2d4-9bf2-ba73-6647-cb9900666de1]]
{{underconstruction}}
==Background and motivation for testing tools==

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

@@ -1,8 +1,6 @@
[[Property:title|Using extracted tests]]
[[Property:weight|5]]
[[Property:uuid|bebd4f28-9818-80f0-a69a-e9ce867723f4]]
{{underconstruction}}
==About extracted tests==

8
documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/using-generated-tests.wiki
View File

@@ -2,10 +2,6 @@
[[Property:link_title|Using generated tests]]
[[Property:weight|7]]
[[Property:uuid|c17ebddf-5d35-76c1-4912-d9f1ca3770a5]]
{{underconstruction}}
==About synthesized tests==
Synthesized tests fill a different role from either extracted or manual tests. The idea behind synthesized tests is that because we specify software through its contracts, and because compliance of the software to those contracts can be actively monitored at runtime, we can know two things necessary for building tests:
@@ -41,7 +37,9 @@ This is where you declare target class(es) for the synthesized tests. You type a
On the right side of the pane you can configure certain options for the synthesizing process.
'''Duration''' controls the length of time the Eiffel Testing Framework will run random invocations of the routines in your target class.
'''Cutoff (minutes)''' lets you specify a number of minutes for the Eiffel Testing Framework to run random invocations of the routines in your target class(es).
'''Cutoff (invocations)''' lets you control how long the Eiffel Testing Framework will run random invocations by declaring a specific number of invocations.
'''Routine timeout''' sets an upper limit on how long the Testing Framework will wait for a random feature call to complete.