Topic: Test Execution

Message

   Test Execution

Manual Tests
Manual
test execution is carried out through the TestDirector user interface
for all manual tests, thus alleviating the need for a hard copy script
to capture test run evidence. A Personal Computer is therefore required
in order to carry out a test run. All activity is electronic so there
is no requirement for paper printouts as evidence supporting a test
run. Evidence supporting a test run can be easily collected during a
test run using a snapshot function which automatically deposits files
securely on the web server and maintains the link to the appropriate
step within the test run. Electronic or digital signatures can be
applied to a test step and/or the end of a test run.

The tester
is allowed to change his mind over a pass/fail decision previously made
in a test run but any change made is documented in accordance with the
audit requirements for electronic records. This allows an auditor to
re-check at any time that the tester’s actions were valid.
A test
run approval facility can be used to record a completed review of any,
or all test run records to suit the level of diligence required. The
approver has the facility to lock each individual test run record from
any further changes if so desired.

Automated Tests
Automated
tests are also initiated only via the TestDirector interface for all
formal test runs. While scripting of automated tests and test dry runs
can be completed free from constraint, formal test runs can be
controlled by TestDirector in the same way as for manual tests. Since
the running of the test is automatic there are no signatures applied
during the test run or to complete the test run.
Results of an
automated test run cannot be changed and a post test run approval
signature can be applied in the same way as for a manual test.

Author	Message
tanushree Senior Member Joined: 04Apr2007 Online Status: Offline Posts: 2160	Topic: Test Execution Posted: 17Oct2007 at 4:08am
	Test Execution Manual Tests Manual test execution is carried out through the TestDirector user interface for all manual tests, thus alleviating the need for a hard copy script to capture test run evidence. A Personal Computer is therefore required in order to carry out a test run. All activity is electronic so there is no requirement for paper printouts as evidence supporting a test run. Evidence supporting a test run can be easily collected during a test run using a snapshot function which automatically deposits files securely on the web server and maintains the link to the appropriate step within the test run. Electronic or digital signatures can be applied to a test step and/or the end of a test run. The tester is allowed to change his mind over a pass/fail decision previously made in a test run but any change made is documented in accordance with the audit requirements for electronic records. This allows an auditor to re-check at any time that the tester’s actions were valid. A test run approval facility can be used to record a completed review of any, or all test run records to suit the level of diligence required. The approver has the facility to lock each individual test run record from any further changes if so desired. Automated Tests Automated tests are also initiated only via the TestDirector interface for all formal test runs. While scripting of automated tests and test dry runs can be completed free from constraint, formal test runs can be controlled by TestDirector in the same way as for manual tests. Since the running of the test is automatic there are no signatures applied during the test run or to complete the test run. Results of an automated test run cannot be changed and a post test run approval signature can be applied in the same way as for a manual test. Post Resume: Click here to Upload your Resume & Apply for Jobs

	IP Logged


One Stop Testing Forum : Testing Tools @ OneStopTesting : TestDirector @ OneStopTesting