Chapter 3 Flashcards
What is static testing?
This type of testing relies on manual examination of work products or tool-driven evaluation of the code or other work products.
What is dynamic testing?
This type of testing involves the execution of the software being tested.
In what type of system is static testing and analysis particularly important?
It is important for safety-critical systems.
It is an important part of security testing and is often incorporated into automated software build and distribution tools.
Name some examples of work products for static testing.
Specifications Epics Code Contracts, project plans Models
What are some benefits to static testing?
It results in early detection of defects before dynamic testing commences. Early defects are cheaper to remove than later defects.
Defects not easily found by dynamic testing are found
Inconsistencies, ambiguity and logic errors are uncovered.
Testing and development time are reduced
Improved team communication
What are the main differences between static testing and dynamic testing?
Static testing finds defects in work products directly while dynamic testing finds defects during the software run.
Static testing can be used to improve the consistency and internal quality of work products, while dynamic testing typically focuses on externally visible behaviours.
Name some typical defects that are easier and cheaper to find through static testing.
Requirement defects Design defects Coding defects Security vulnerabilities Deviations from standards
What is the difference between a formal and informal review?
Informal review involves not following a defined process and not having formal documented output.
Describe the steps of the review process.
Planning: The scope of review is defined. The time and effort is estimated.
Initiate review: Distribute work product, Explain scope, goals, process etc., Answer participant questions about review
Individual review: Review all or part of work product, Noting defects, recommendations and questions
Issue communication and analysis
Fixing and reporting
List and describe the typical review roles
Author: creator of the work product. Also fixes defects in the work product
Management: responsible for review planning. Assigns staff, budget and time
Facilitator: Mediates and ensures effective running of review meetings
Review leader: Takes responsibility for review. Decides who, when and where in the review.
Reviewers: SMEs, team members, stakeholders. Job titles are diverse. They identify the potential defects.
Scribe: recorder of the meetings.
List some review types
Informal review
Walkthrough
Technical review
Inspection
List some review techniques.
Ad-hoc
Checklist based
Scenarios and dry runs
Role-based
Define entry criteria.
Entry criteria are the criteria or requirements, which must be met before initiating a specific task or a process.
Define exit criteria.
Exit criteria are the requirements which must be met to complete a specific task or process
Describe a walkthrough.
The author of the document under review explains the document to stakeholders of different backgrounds. The stakeholders may point out defects by way of scenarios or dry runs. The author does most of the preparation and the document is usually high level. A scribe may attend.