Term
|
Definition
| Testing a work product without the code being executed. |
|
|
Term
|
Definition
Static Testing is defined as a software testing technique by which we can check the defects in software without actually executing it.
Its counter-part is Dynamic Testing which checks an application when the code is run.
Static testing is done to avoid errors at an early stage of development as it is easier to find sources of failures then failures themselves.
Static testing helps to find errors that may not be found by Dynamic Testing.
The two main types of static testing techniques are:
1. Manual examinations.
Manual examinations include analysis of code done manually, also known as REVIEWS.
2. Automated analysis.
Automated analysis is basically static analysis which is done using tools. |
|
|
Term
|
Definition
A review in Static Testing is a process or a meeting conducted to find the potential defects in the design of any program. Another significance of the review is that all the team members get to know about the progress of the project and sometimes the diversity of thoughts may result in excellent suggestions. Documents are directly examined by people and discrepancies are sorted out.
Reviews can further be classified, as:
Informal reviews.
Walkthroughs.
Technical review.
Inspections. |
|
|
Term
|
Definition
Static testing is performed due to the following reasons:
Early defect detection and correction.
Reduced development timescales.
Reduced testing cost and time.
For improvement of development productivity.
To get fewer defects at a later stage of testing. |
|
|
Term
| What is Tested in Static Testing |
|
Definition
Unit Test Cases.
Business Requirements Document (BRD).
Use Cases.
System/Functional Requirements.
Prototype.
Prototype Specification Document.
DB Fields Dictionary Spreadsheet.
Test Data.
Traceability Matrix Document.
User Manual/Training Guides/Documentation.
Test Plan Strategy Document/Test Cases.
Automation/Performance Test Scripts. |
|
|
Term
| Activities for performing Static Testing |
|
Definition
1. Use Cases Requirements Validation: It validates that all the end-user actions are identified, as well as any input and output associated with them. The more detailed and thorough the use cases are, the more accurate and comprehensive the test cases can be.
2. Functional Requirements Validation: It ensures that the Functional Requirements identify all necessary elements. It also looks at the database functionality, interface listings, and hardware, software, and network requirements.
3. Architecture Review: All business level processes like server locations, network diagrams, protocol definitions, load balancing, database accessibility, test equipment, etc.
4. Prototype/Screen Mockup Validation: This stage includes validation of requirements and use cases.
5. Field Dictionary Validation: Every field in the UI is defined well enough to create field level validation test cases. Fields are checked for min/max length, list values, error messages, etc. |
|
|
Term
| Static Testing Techniques |
|
Definition
|
|
Term
| Tips for Successful Static Testing Process |
|
Definition
Focus only on things that really count.
Explicitly plan and track review activities. A software walkthrough and inspection are generally composite into peer's reviews.
Train participants with examples.
Resolve people issues.
Keep process formal as the project culture.
Continuous Improvement – Process and Tools.
By removing the major delays in test execution, testing cost and time can be reduced. |
|
|
