Static Techniques Flashcards
What is static testing?
Static Testing is the examination of program source code or other project documentation, without the execution of the code, to find the defects.
What are reviews in static testing?
Manual examination of documents - done by humans.
What is static analysis?
automated analysis of source code and software - done by tools.
Wha is dyanmic testing?
testing performed by executing software undr test and comparing actual vs. expected results.
What is the difference between static and dynamic testing?
Static testing will aim at find causes of failuders directly while dynamic will find failures which might be caused by defects.
What are some typical documents that get reviewed?
Business requirements, functional specifications, system and database design, source code, test plans, etc..
What are some benefits of conducting reviews?
Early defect detection and correction, increased dev productivity, reduced dev cost, fewer defects in code, reduced time and cost of dynamic testing.
What is the goal of a review?
The goals of reviews are to verify and validate document against specifications, being consistent with previous documents, and completennes and conformance to stanards.
What is the structure of a review?
Planning - kick-off individual preparation - review meeting - re-work - follow-up
Reviews - what is planning?
Where the intiial decisions are made, for example the criteria to review, the people who willk review.
Reviews - what is a kick-off?
Documents being distributed 3 days prior to the meeting
Reviews - what is individual preparation?
The attendees will review the documents and make notes on potential defects they found etc..
Reviews - what is the review meeting?
The meeting where the review is held. Managed by the moderator to ensure it is on track.
Reviews - what is the rework?
The authour will correct the document
Reviews - what is the follow-up?
The moderator ensures the document has been corrected and collects metric on for example time spent reviewing.
Reviews - what is a manager?
decides the execution of the review and may not participate.
Reviews - what is a moderator?
the one responsible for managing all review team activities. He plans, motitivates, facilitates, trains, and monitor. He should be trained in this process.
Reviews - what is the author?
The one preparing the material to be reviewed.
Reviews - what are the reviewers?
The ones responsible for finding defects, should have experience on the system and would be ideal to have them from different areas of the business.
Reviews - what is the scribe?
Documents all the issue, etc..
What are the different types of review?
Informal - walkthrough - technical review - inspection.
What is an informal review?
One to one, no formal process. Inexpensive.
What is walkthrough review?
Meeting led by the author. Might be a dry scenario, or peer group. The objective is to present information and learn.
What is a technical review?
Documented, well defined, with a moderator. Will use guidelines or checklists. A review report is sent out at the end.
What is an inspection review?
Vey thorough, has a process. There needs to be entry criteria. There is a moderator, documents will likely be created.
What are success factors in reviews?
Clear predefined objectives, right people, testers are valued, defects are welcomed, atmosphere of trust.
What are checklists in reviews?
A set of questions usually from one perspective (tester, developer, etc..)
What are the benefits of static analysis?
It allows to provide early detection of defects, it can help prevent further defects.
What are some examples of defects found by static analysis?
Looping code, unreachable code, data flow analysis.
What is a looping code?
A continuous loop running forever.
What is unreachable code?
A piece of code that cannot be reached.
What is data flow analysis?
Understanding if variables are used or not.
Why use static analysis tools and what are they?
These are tools that can be used to review the code. Allow to locate complex source code, produce graphics, design structural tests, examine source code from a number of perspectives.
