Static Testing Activities

Static Testing

The simple static test is essential to detect the possible defects or errors during design stage of software applications & to verify in a precise modus or the various tasks for synthesis of program modules & the test plans. Some of activities that relate to the static testing involve desk checks, code inspections, or walkthroughs. You should also note that’s the static testing is conducted without need to execute the program. The software developer just requires to analyzing the data & the codes that are within program. One of important tasks of conducting the static testing is to search for the possible bugs in program. You can find the various bugs in software’s applications.

The two main activities of static testing are that:

·         Reviews

·         Testing with use of tools.

Review:

The Review activities of static testing can be formal & in-formal. The in-formal activities are used more often that formal, & in both cases, re-viewed document can be checked more than once. Another classification of re-view activities divides into three different groups:

·         Software walk-through.

·         Technical re-view.

·         Software’s inspection.

A Software walkthroughs & inspections are generally composite into peer’s re-views.

A Static testing with use of automated testing tool’s is effected prior of code run or help’s to inspect the design, code or other testing activities. This type of static testing that aims to checks the code of software’s & uses by the following tools:

·         Metrics of code.

·         Structure of code.

·         Code conformity with modern standards.

Benefits of Reviews:

·         Development productivity can be increased & time reduced.

·         Testing costs & time can be reduced through removing the main delays in test execution.

·         Reduction in life-time costs can be achieved.

·         Improved the communication outcomes as authors & discuss with peers.

Different objectives of re-views:

·         Finding Bugs

·         Generating discussions.

·         Gaining understanding.

·         Decision making by consensus.

Activities of formal Review:

The Reviews at more formal end of spectrum, such as technical re-views & inspections, share the certain characteristics of that different them from the less formal re-views of which walkthrough are a typical example.

Stages of formal reviews:

·         Planning

·         Re-view entry criteria

·         Kick-off

·         Review Meeting

·         Individual Preparation

·         Examine

·         Fixing Defects

·         Follow-up

·         Checking Exit Criteria

General role & responsibilities of different members in re-view team:

·         Manager

·         Moderator

·         Author

·         Re-viewers

·         Scribe