Fundamental
Test Process:
It involves planning, specification, execution,
recording and checking for completion.
·
Specification:
It involves designing test cases and test conditions using Test techniques identified at the
planning stage. It is important to determine the expected results prior to test
execution.
Test Techniques
1. Formal technical review:
A formal technical review is conducted by the software quality assurance
group. It examines only a small part of
the software project. Only one developer is responsible for the artifact. The artefact
is examined on various levels. It includes things like function and logic as
well as implementation. It ensures that all artifacts of the project developed
in a uniform manner. Typically a review will last 2 hours. The review may consist of walk-through s, code inspections or any other
examination. Since the purpose of a review is to find errors, a review can
be difficult to control
2. Code walk-through :
A source code walk through often is called a
technical code walk through or a peer code review. The typical scenario finds a
developer inviting his technical lead, a database administrator, and one or
more peers to a meeting to review a set of source modules prior to production
implementation. Often the modified code is indicated after the fact on a hard copy listing with annotations or a highlighting pen, or within the code
itself with comments.
A code walk through is an effective tool in the
areas of quality assurance and education. The developer is exposed to alternate
methods and processes as the technical lead and database administrator suggest
and discuss improvements to the code. The technical lead is assured of an
acceptable level of quality and the database administrator is assured of an
acceptable level of database performance. The result is better performance of
the developer, his programs, and the entire application.
Despite all the benefits of source code
walk through s, few organizations implement and enforce them as a shop standard.
Many excuses are given, but each has a practical solution.
·
Execution:
It involves running the specified test on a
computer system either manually or by using an automated test tool.
·
Recording:
It involves keeping good records of
the test. The tested versions, the tested specifications of software and the
test specifications are recorded along with the actual outcome of each test.
·
Successful
tests detect faults:
A successful test is one that detects a
fault and may cause a delay.
·
Completion
or exit criteria:
Completion or exit criteria are used to determine when testing is
complete. It may be defined in terms of cost, time, faults found or coverage
criteria.
·
Coverage
criteria:
Coverage criteria are defined in terms of items that are exercised by
test suites, such as branches, user requirements, most frequently used
transactions etc
