diff --git a/documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/create-manual-test.wiki b/documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/create-manual-test.wiki index 66e01e9e..1e2beeed 100644 --- a/documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/create-manual-test.wiki +++ b/documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/create-manual-test.wiki @@ -78,7 +78,7 @@ end You shouldn't let it worry you if you've noticed that the class BANK_ACCOUNT contains some flaws. We'll deal with these later. -If you want to work along with this tutorial, you should be able to copy the text of each these classes from this page and paste it into the EiffelStudio editor pane. Build a system using these two classes. +If you want to work along with this tutorial, you should be able to copy the text of each these classes from this page and paste it into the EiffelStudio editor pane. Build a system using these two classes, and {APPLICATION}.make as the root. {{note|If you are using EiffelStudio version 6.3, there two things you will need to do to prepare your system for use with the Eiffel Testing Framework. Both of these are done from the [[EiffelStudio: Project settings window]].
1) Set your project to be a console application in the [[Advanced options]].
2) Set a value of False for the Recursive attribute of your project cluster in [[Group options]].}} diff --git a/documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/execute-tests.wiki b/documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/execute-tests.wiki index 0433b83e..e4615d18 100644 --- a/documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/execute-tests.wiki +++ b/documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/execute-tests.wiki @@ -109,7 +109,7 @@ The advantage of using the Eiffel Testing Framework is that the test that we wro ==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. +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 types 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. diff --git a/documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/index.wiki b/documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/index.wiki index 38af4014..032345c3 100644 --- a/documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/index.wiki +++ b/documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/index.wiki @@ -10,4 +10,8 @@ The Eiffel Testing Framework is a tool that helps you to create, manage, and run tests against your software. The Eiffel Testing Framework is accessible directly as a part of EiffelStudio, but works to a large extent behind the scenes so that it doesn't get in the way of your development activities. In other words, even though you may be accumulating a substantial collection of test software along with your project software, you can still run and deliver your project software without going to a lot of trouble separating the two. Tests managed by the Eiffel Testing Framework stay handy and can be run any time to help make sure everything always stands up to the scrutiny of testing. +{{note|It is recommended, at least on your first viewing of this documentation, that you take the sections in the order in which they are presented. There are three different types of tests supported by the Eiffel Testing Framework. The topic of creation and use of each type of test occupies its own page. But to avoid repetition, the second and third pages omit some of the detail in the first and assume a familiarity with the example. }} + + + diff --git a/documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/using-generated-tests.wiki b/documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/using-generated-tests.wiki index 70c3bca6..760a7567 100644 --- a/documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/using-generated-tests.wiki +++ b/documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/using-generated-tests.wiki @@ -51,9 +51,13 @@ The last check box, '''Create HTML output''' give you the option of having the E [[Image:Testing Framework synthesized complete dialog]] -The view the result summary, navigate to the result subdirectory of the directory shown in the dialog, then open the file index.html with your browser. +To view the result summary, navigate to the result subdirectory of the directory shown in the dialog, then open the file index.html with your browser. -In fact, if we try to synthesize tests on the class BANK_ACCOUNT in which we have already fixed bugs, we will see something about like the following results: + +{{note|The result directory includes files that summarize the whole synthesized testing process. Some of these are lengthy because they contain information on test cases used for each target routine. }} + + +In fact, if we try to synthesize tests on the class BANK_ACCOUNT in which we have already fixed two bugs after the manual and extracted tests, we will see something about like the following results: [[Image:Testing Framework synthesized results pass]] @@ -69,6 +73,7 @@ If we re-introduce the bug into the deposit procedure of class -{{note|If you've been working along in EiffelStudio, you may notice that your synthesized class looks slightly different. }} +{{note|If you've been following along by the doing these examples in EiffelStudio, you may notice that your synthesized class looks slightly different. }} This test is written in a way that is a little different from both the manual test we wrote and the extracted test. But it's not too hard to figure out what's going on. An object of type BANK_ACCOUNT will be created (local v_6) and the deposit feature will be applied to it with an argument value of 3 (local v_7). @@ -125,7 +130,7 @@ You can see that this test, although it is implemented differently, is about the [[Image:Testing Framework interface after run 05]] - +If we replace the implementation for {BANK_ACCOUNT}.deposit that we had removed, and then re-execute the tests, all are successful.