Static Testing
- 1. Static Testing Presented By : - Suraj Vishwakarma
- 2. Outlines What is Static Testing Tools for Static Testing Participants in Static Testing Static Testing Techniques Advantages of Static Testing Disadvantages of Static Testing Success factors for review
- 3. • software testing technique in which the software is tested without executing the code. • Static testing is a software testing method that involves examination of program's code and its associated documentation. • Also called as Dry-Run Testing. • Programmers find any errors. Hence named ‘static’. • Static testing is a stage of White Box Testing. What is Static Testing
- 4. What is Static Testing • Main objective of this testing is to improve the quality of software. • Finding errors in early stages of the development cycle. • Most static testing techniques can be used to ‘test’ any form of document including source code, design documents and models, functional specifications and requirement specifications.
- 5. What is Static Testing Static Testing Review Static analysis
- 6. Customer Level Function Level Software Architecture Module Design Implementation Static Testing Requirement Design Implementation Verification Maintenance Product Requirement documents Software Architecture Software
- 7. Tools for Static Testing / Static Analysis - By Tools: • Following are the types of defects found by the tools during static analysis: • A variable with an undefined value • Variables that are declared but never used • Unreachable code (or) Dead Code • Programming standards violations • Security vulnerabilities(weakness reduce system information) • Syntax violations
- 8. Participants in Static Test Moderator Author Scribe Reviewer Manager During a review five types of participants take part. They are:
- 9. Participants in Static Testing The moderator • Also known as review leader • Performs entry check • Follow-up on the rework • Schedules the meeting • Coaches other team • Leads the possible discussion and stores the data that is collected
- 10. Participants in Static Testing The author • Illuminate the unclear areas and understand the defects found • Basic goal should be to learn as much as possible with regard to improving the quality of the document. The scribe • Scribe is a separate person to do the logging of the defects found during the review.
- 11. Participants in Static Testing The reviewers • Also known as checkers or inspectors • Check any material for defects, mostly prior to the meeting • The manager can also be involved in the review depending on his or her background. The managers • Manager decides on the execution of reviews • Allocates time in project schedules and determines whether review process objectives have been met
- 12. Static Testing Techniques / Types of Reviews Informal Reviews Formal Reviews Technical Reviews Walk Through Inspection Process Static Code Review Low High
- 13. Informal Review • Doesn't follow any process to find errors in the document, you just review the document and give informal comments on it. • Applied many times during the early stages of the life cycle of the document. • A two person team can conduct an informal review and in later stages more people are involved. • The most important thing to keep in mind about the informal reviews is that they are not documented
- 14. Formal Review Formal reviews follow a formal process. It is well structured and regulated (Controlled). A formal review process consists of six main steps: 1. Planning 2. Kick-off 3. Preparation 4. Review meeting 5. Rework 6. Follow-up
- 15. Technical Review • A team consisting of your peers, review the technical specification of the software product and checks whether it is suitable for the project. • They try to find any discrepancies in the specifications and standards followed. • This review concentrates mainly on the technical document related to the software such as Test Strategy, Test Plan and requirement specification documents.
- 16. Walkthrough • The author of the work product explains the product to his team. • Participants can ask questions if any. • Meeting is led by the author. • Scribe makes note of review comments
- 17. Inspection • The main purpose is to find defects and meeting is led by trained moderator. • This review is a formal type of review where it follows strict process to find the defects. • Reviewers have checklist to review the work products . • They record the defect and inform the participants to rectify those errors.
- 18. Static Code Review • This is systematic review of the software source code without executing the code. • It checks the syntax of the code, coding standards, code optimization, etc. • This is also termed as white box testing. • This review can be done at any point during development.
- 19. Advantages of Static Testing • Since static testing can start early in the life cycle so early feedback on quality issues can be established. • As the defects are getting detected at an early stage so the rework (Revise and rewrite) cost most often relatively low. • Development productivity is likely to increase because of the less rework effort.
- 20. Disadvantages of Static Testing • Time consuming as conducted manually. • Does not find vulnerabilities (Harm) introduced in runtime environment. • Limited trainee personnel to thoroughly conduct static code analysis.
- 21. Thank You