This project is read-only.

Executing the (re)tests

To obtain test results, on the basis of which evaluation of the test object can take place.

The method of operation includes the following subactivities:
  • Executing dynamic explicit tests
  • Executing dynamic implicit tests
  • Executing static tests.

dynamic explicit testing

In dynamic explicit testing, explicit test cases are executed to obtain information on the property (quality characteristic) or system part under test. Results are compared in the subsequent activity against the expected results, thus delivering any defects.

There are two possible types of dynamic explicit testing:
  • Testing on the basis of specified tests created in the Specification phase. The specified tests that are created in the Specification phase form the starting point for the tests to be executed here. The place to start running test case in Testing Center is the ‘Test’ menu, from there the tester who executed the tests can run selections of different tests.
Cannot resolve image macro, invalid image name or id.
When a tester starts a test case for execution Testing Center starts an additional tool called ‘Test runner’. This tool supports the testers in the steps he needs to fulfill in the test case.
Cannot resolve image macro, invalid image name or id.
More information about running test cases can be found on MSDN: url: Running Manual Tests Using Test Runner
  • Testing on the basis of an exploratory technique.
A quick way of helping inexperienced testers on their way is to carry out this activity in pairs. Team up an inexperienced tester with an experienced one Kaner, 2001. In this, one tester is responsible for the test. He involves another tester, with one of them operating the keys and the other thinking about the things to be tested, observing, taking notes and researching. By thinking aloud, the testers together generate many more ideas than they would separately. They also help each other not to lose sight of the test goal because of unimportant details. Coaching in pairs is certainly to be recommended, particularly in the beginning. Testing in pairs is less successful if the individuals are very introverted or very assertive.

With this type, the tester carries out exploratory work during the dynamic explicit test. This means that the tester is examining the application under test piece by piece, thinking about what should be or could be tested. Possible techniques are “Exploratory Testing” and “Error Guessing”. Although Testing Center is specially build for testing on the basis of specified tests it is still possible to use it for exploratory testing. With exploratory testing the test design and test execution are very close to each other, every step the tester decides designs what his next step is going to be execute. So, it isn’t possible to create pre-defined test cases with their steps upfront for exploratory testing. To still have the possibility of bug reporting and the connection with developers there needs to be just one test case. This test case can be re-used for every exploratory test. When failing the bug is filled with all the necessary information for the developer to reproduce the steps the exploratory tester executed. Information what the tester did is overwritten when an other exploratory test case is executed from that test case also this information isn’t available in reporting. When you do want to save this information and want to make it available in reports, a new test case needs to be created every time an exploratory test begins.

Cannot resolve image macro, invalid image name or id.
Submitting a bug

dynamic implicit tests

During dynamic explicit testing, information can also be gathered on other properties (quality characteristics). No explicit test cases are designed for these. This is referred to as dynamic implicit testing, and the tests can be executed planned or unplanned.

Unplanned implicit testing arises because, during execution of the test, certain things start to catch the attention. It is agreed to observe them more closely. If, for example, regular system breakdown takes place, a decision can be taken as regards reliability. Alternatively, if certain screens do not have an appealing look and feel, something can be said about the usability.

Submitting findings for dynamic implicit testing can been done during the execution of dynamic explicit test, more than one bug can be submitted during the execution of a test case. Also comment can be added during the execution of a test. See on MSDN: How to: Attach a Comment While Running a Test.

Cannot resolve image macro, invalid image name or id.

Executing static tests

It is laid down in the test strategy whether static tests should be carried out. In static testing, end products are assessed without any software being run. This test usually consists of the inspection of documentation, such as security procedures, training, manuals, et cetera and is often aided by checklists. On the basis of these, it is attempted to obtain insight into the relevant quality aspect. Here too, any defects are registered and processed by means of the defects procedure.

Last edited Nov 7, 2009 at 7:09 AM by ClemensReijnen, version 8


No comments yet.