1
Q
Static Analysis
A
- Automated activity
- Performed on the code
- Security Testing
- For safety-critical computer systems
- Applied efficiently to any work product
- With tools that evaluate work products written in natural language
- Checking for spelling
- grammar
- readability
- Formal structure
2
Q
Benefits of Static Testing
A
- The relative cost of fixing defects
- Saves time and money
3
Q
Defects that are easier to find and fix in Static Testing
A
- Requirements defects
- Design defects
- Coding defects
- Deviations from standards
- Incorrect interface specifications
- Security vulnerabilities
- Gaps or inaccuracies in test basis traceability or coverage
- Maintainability defects
4
Q
Which TWO of the following statements about static testing are MOST true?
A
→ A cheap way to detect and remove defects
→ Early validation of user requirements
5
Q
Which of the following techniques is a form of static testing?
A
→ Code review
6
Q
What is the main difference between static and dynamic testing?
A
→ Dynamic testing requires executing the software, the software is not executed during static testing
7
Q
Planning review
A
- Defining the scope
- Estimating effort
- Identify review characteristics, types, roles
- Selecting the people to participate in the review and allocating roles
- Defining the entry and exit criteria (our goals)
- Checking those entry criteria are met
8
Q
Initial Review
A
- Distributing the work
- Explaining the scope, objectives, process, roles, and work products
- Answering any questions that participants may have about the review
9
Q
Individual Review
A
- Reviewing all parts of the work product
2. Noting potential defects, recommendations, and questions
10
Q
Issue Communication and Analysis
A
- Communicating identified potential defects (review meeting)
- Analyzing potential defects, assigning ownership and status to them
- Evaluating and documenting quality characteristics
- Evaluating the review findings against the exit criteria to make a review decision
11
Q
Fixing and Reporting
A
- Creating defect reports
- Fixing defects found
- Communicating defects to the appropriate person or team
- Recording updated status of defects
- Gathering metrics
- Checking that exit criteria are met
- Accepting the work product when the exit criteria are reached
12
Q
Author
A
- Create the work product under review
2. Fixed defects in the work product under review
13
Q
Manager
A
- Is responsible for review planning
- Executes control decisions in the event of inadequate outcomes
- Decides on the execution of reviews
- Assigns staff, budget, and time
- Monitors ongoing cost-effectiveness
14
Q
Facilitator or Moderator
A
- Ensures effective running of review meetings
- Mediates, if necessary, between the various points of view
- Is often the person upon whom the success of the review depends
15
Q
Review leader
A
- Takes overall responsibility for the review
2. Decides who will be involved and organizes when and where it will take place
16
Q
Reviewers
A
- Maybe subject matter experts, persons working on the project
- Identify potential defects in the work product under review
- May represent different perspectives
17
Q
Scribe or recorder
A
- Collates potential defects found during the individual review activity
- Records new potential defects, open points, and decisions from the review meeting
18
Q
Informal review, buddy check, pairing, pair review
A
- Detecting potential defects
- Generating new ideas or solutions
- Quickly solving minor problems
- Optional → Results documentation and checklists
- May be performed by a colleague of the author
- Not based on a formal process
- May not involve a review meeting
- Varies in usefulness depending on the reviewers
- Very commonly used in Agile
19
Q
Walkthrough
A
- Find defects, improve the software product, consider alternative implementations, evaluate conformance to standards and specifications
- Exchanging ideas about techniques or styles
- Training of participants
- Optional → Individual preparation , checklists, defect logs and review reports
- Mandatory → Scribe
- Review meeting is typically led by the author of the product
- May take the form of scenarios, dry runs
- May vary in practice from quite informal to very formal
20
Q
Technical Review
A
- Gaining consensus, detecting potential defects
- Evaluating quality and building confidence in the work product
- Generating new ideas
- Motivating and enabling authors to improve future work products
- Optional → Review Meeting, checklists, defect logs and review reports
- Mandatory → Individual preparation, scribe (not the author)
- Reviewers should be technical peers of the author, and technical experts
21
Q
Inspection
A
- Detecting potential defects, evaluating quality and building confidence in the work product, preventing future similar defects through author learning and root cause analysis
- Mandatory → defined process, checklists, clearly defined roles, individual preparation, entry and exit criteria, scribe, gathering metrics, defect logs and review report
- May include a dedicated reader, who reads the work product aloud
- Review meeting is led by a trained facilitator, no the author
- Author cannot act as the review leader, reader or scribe
22
Q
The main purposes of ….. review type include: improving the software product, considering alternative implementations and finding defects.
A
Walkthrough
23
Q
In the ‘’Walkthrough’’ review type the ….. is mandatory and the leader of the review meeting is the …………… .
A
→ scribe / author of the work product
24
Q
In the ‘’Technical review’’ type, the ….. are mandatory, and the technical peers of the author are the …… .
A
→ individual preparation and scribe / reviewers
25
The purposes of ….. review type include: preventing future similar defects through author learning and root cause, and achieving consensus.
→ Inspection
26
Ad Hoc
1. Reviewers are provided with little or no guidance on how this task should be performed
2. Reviewers often read the work product sequentially, identifying and documenting issues as they encounter them
3. Is a commonly used technique needing little preparation
4. Is highly dependent on reviewer skills and may lead to many duplicates issues
27
Checklist-based
1. Systematic technique, whereby the reviewers detect issues based on checklists that are distributed at review initiation
2. Set of questions based on potential defects, which may be derived from experience
3. Systematic coverage of typical defects types
4. Check defects outside the checklist
28
Scenario and dry runs
1. Reviewers are provided with structured guidelines on how to read through the work product
2. Approach supports reviewers in performing “dry runs” on the work product based on the expected usage of the work product.
3. These scenarios provide reviewers with better guidelines on how to identify specific defect types than simple checklist entries
4. Reviewers should not be constrained to the documented scenarios
29
Role-based
1. Is a technique in which the reviewers evaluate the work product from the perspective of individual stakeholder roles
2. Typical roles include specific end user types (experienced, senior) and specific roles in the organization (user administrator, performance tester)
30
Perspective-based
1. Reviewers take on different stakeholder viewpoints in individual reviewing
2. Typical stakeholder viewpoints include end user, marketing, designer, tester, or operations
3. Leads to more depth in individual reviewing with less duplication of issues across reviewers.
4. Most effective general technique
ISTQB
flashcards
Decks in class (16)
# Cards
