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

Author:halw

Browse Source 
Date:2009-02-26T18:44:19.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@198 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2009-02-26 18:44:19 +00:00
parent c3aa41677c
commit c5853999f5
2 changed files with 15 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -28,6 +28,12 @@ If you want to remove a whole test set, then [[Removing a class|delete the class
==Using Views and Filters==
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]].
Filters control ''which'' tests are displayed in the Eiffel Testing Framework interface.
===The View box===
The View box on the Eiffel Testing Framework can be used to display tests by different criteria. However, the workings of the View box deserve some explanation. If you just try to use View without any background knowledge, you may find it non-intuitive.
@@ -36,7 +42,7 @@ It is important to bear in mind that the View box works with the system of [[Cre
When the View box is displaying a set of tests, the "root" tag(s) for the sub tree of tests is what is visible in the View box. Let's look at some examples.
If the view box is empty, it will display all tests, accessible through all root tags. So, using the example we built in the preceding sections, if we just select the blank choice for the View box, here's what we see:
If the view box is empty, it will display tests accessible through all root tags. So, using the example we built in the preceding sections, if we just select the blank choice for the View box, here's what we see:
[[Image:Testing Framework interface View box 01]]
@@ -112,11 +118,17 @@ and in the synthesized test which targets <code>{BANK_ACCOUNT}.withdraw</code> w
<code>
testing: "my_tag_1/my_tag_1_2/my_tag_1_2_1"
</code>
As soon as we compile and look at the View box, we see that the root for our new tag shows up. And if we expand it completely, we find the test that we tagged.
As soon as we compile and set the View box to blank to show all tag roots, we see that the root for our new tag root shows up in the list:
[[Image:Testing Framework interface View box 07]]
If we expand the tag root '''my_tag_1''' completely, we see our tests arranged according to their values for this tag root:
[[Image:Testing Framework interface View box 08]]

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

@@ -108,7 +108,7 @@ In its simplest form, a test is a routine that issues a call to some routine you
So the tests and the test classes are in the realm of testing and are used to test the target routines in target classes which are the real product of your software development project.
Even though the test shown above doesn't test anything, it still qualifies as a test. The Eiffel Testing Framework will manage and run the tests in any test class whether or not they actually test any target routines. Naturally, it would seem silly to keep a test around that doesn't test anything, but the important thing to understand is that the Eiffel Testing Framework will work with anything that matches the definitions of test and test class above. That is, once tests are created, the Eiffel Testing Framework doesn't really have a stake in what you are trying to test.
The Eiffel Testing Framework will manage and run the tests in any test class whether or not they actually test any target routines. Naturally, it would seem silly to keep a test around that doesn't test anything, but the important thing to understand is that the Eiffel Testing Framework will work with anything that matches the definitions of test and test class above. That is, once tests are created, the Eiffel Testing Framework doesn't really have a stake in what you are trying to test.
Take a look at the following test class: