Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

QA REVIEW > Chapter 1 > Flashcards

Chapter 1 Flashcards

1
Q

For each test level, Test Planning starts when?

A

INITIATION of the test process and

Continues throughout the project until completion of CLOSURE ACTIVITIES

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Test Planning identifies what?

A
  1. Activities and Resources
  2. Methods - Metrics
    - gathering and tracking METRICS
  3. Adherence to plan
  4. Assess achievement of the objectives
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

How to determine useful METRICS during test planning stages?

A
  1. TOOLS selected
  2. TRAINING scheduled
  3. DOCUMENTATION established
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Test Strategies selected help to determine what?

A

TASKS that occur during the planning stages

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

RISK-BASED Test Strategy

A

RISK ANALYSIS

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q
  • to guide test planning process to MITIGATE the reduction of risks
  • to help in contingency planning
A

RISK ANALYSIS

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

If a number of likely and serious potential defects related to security are identified, what shall be done?

A

Significant amount of effort should be spent developing and executing security tests.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

If serious defects are usually found in the design specifications, what shall be done?

A

Test planning process could result in ADDITIONAL STATIC TESTING (Reviews) of design specifications.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Which is used to determine the priorities of various testing activities?

A

RISK INFORMATION

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What should be conducted if system performance is at high risk?

A

Performance testing may be conducted as soon as integrated code is available

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Planning for the creation of

  • test charters and tools
  • DYNAMIC TESTING TECHNIQUES
  • EXPLORATORY TESTING
A

Reactive Strategy

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Test Planning defines what?

A

Test Approach
Test Levels
Goals and Objectives per level
Test Techniques

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Risk-based testing - AVIONICS

A

Risk-Assessment

  • level of code coverage is required
  • which testing techniques to use
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

External dependencies and SLAs

A 
Resources from outside group
Dependencies on other projects or working within a program 
Deployment team
External vendors or Devt partners
DB administrator
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Efficient TEST CONTROL

A

Testing Schedule

Monitoring Framework

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Test Framework includes these and to meet test objectives and test coverage

A

MEASURES and TARGETS

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

This is the ability to report on traceability status makes complex relationship between devt work work products, test basis, test work products more transparent and comprehensive

A

PROPER CONFIGURED TRACEABILITY

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Stakeholder measures and tatgets

A

Coverage on operational business cycle

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

TEST CONTROL

A
  • ongoing activity
  • compares actual progress against the plan
  • implements corrective actions
  • guides testing to fulfill the mission, strategies, and objectives
  • revisits test planning activities
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

It is the activity that defines “WHAT IS TO BE TESTED” in the form of test conditions

A

TEST ANALYSIS

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Can be identified by analysis of the test basis, test objectives and product risks

A

TEST CONDITIONS

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Test conditions are traceable back to?

A
  • test basis and
  • strategic objectives
  • test objectives
  • other project or stakeholder criteria for success
23
Q

Test conditions are traceable forward to?

A
  • test designs and

- other test work products

24
Q

Can be used to identify test conditions

A

FORMAL TECHNIQUES
ANALYTICAL TECHNIQUES
- Risk-Based Strategies
- Requirement-Bars Strategies

25
Q

Factors to consider on deciding the level of detail at which to specify test conditions

A
  1. Level of testing - High/Low
  2. Level of detail and quality of the test basis
  3. System software complexity
  4. Project and product risk
  5. Relationship between the test basis what is to be tested and how it is to be tested
  6. Software development lifecycle in use
  7. Test management tool being utilized example test director
  8. Level at which test design and other test word products are to be specified and documented
  9. Skills and knowledge of the test analyst
  10. Level of maturity of the test process and the organization itself (note that higher maturity may require a greater level of detail or allow a lesser level of detail)
  11. Availability of other project stakeholders for consultation
26
Q

Advantages of Detailed Test Conditions

A
  1. Flexibility in relating other test work products example test cases to the test basis and test objectives thus, providing better and more detailed monitoring and control for a test manager
  2. Defect prevention
  3. Relates testing work products to stakeholders in terms that they can understand
  4. Influence and direct other development activities
  5. Enables test design, implementation and execution, together with the resulting word products to be optimized by more efficient coverage of detailed measures and target
  6. Basis for clearer horizontal traceability
27
Q

Disadvantages of detailed test conditions

A
  1. Time consuming
  2. Maintainability ability can be difficult in a changing environment
  3. Level of formality needs to be defined and implemented across the team
28
Q

Specification of detailed test conditions can be particularly effective in the following situation

A
  1. Light weight test design documentation methods such as checklists are being used due to accommodate the development lifecycle cost and time constraints or other factor
  2. Little or no formal requirements or other development work products are available as the test basis
  3. Project is large scale, complex or high risk and requires a level of monitoring and control that cannot be delivered by simply relating test cases to development work products
29
Q

Test conditions may be specified as LESS DETAIL when the test bases can be related easily and directly to the test word products this is more likely to be the case for the following

A
  1. Component level testing
  2. Less complex projects where simple simple hierarchical relationships exist between what is to be tested and how it is to be tested
  3. Acceptance testing where use cases can be utilized to help define tests
30
Q

What is the activity that defines how something is to be tested?

A

TEST DESIGN

31
Q

TEST DESIGN

A

TEST CASES

32
Q

Test data creation during Iterative Approach can be done in what test process?

A

Test Design

33
Q

Activity during which tests are organized and prioritized by the test analysts

A

TEST IMPLEMENTATION

34
Q

STANDARD define

  • inputs and expected results in test case specs and
  • test steps in test procedures specs
35
Q

Disadvantages of EARLY TEST IMPLEMENTATION

A

AGILE: Iterative

  • code changes dramatically iteration to iteration results in significant changes
  • code becomes obsolete
  • scripted tests/auto script unreliable or high maintenance

SEQUENTIAL:
- requirements chg frequently

36
Q

ADVANTAGES of EARLY IMPLEMENTATION

A
  1. Worked examples how sw shd behave
  2. Concrete tests written based on test basis are easier for business experts to find verification than abstract
  3. Identify weakness in sw specs
  4. Verified tests illuminate illustrations of required behavior for sw designers and developers
37
Q

Test Manager’s Role (Test Execution)

A
  1. Monitor progress accdg to Test Plan
  2. Initiate, carry out CONTROL actions to guide testing towards successful conclusion:
    MISSION
    OBJECTIVE
    STRATEGY
38
Q

Checking against implicit and explicit entry criteria

A

Test Implementation

39
Q

Test a implementation involves what?

A
  1. FINAL CHECKS - ready to test
    - ensures delivery of
    ——test envt
    ——code
    ——test data
    ——/RUN ENVT AND ACCEPTANCE TESTS
    - test cases are all
    ——written
    —-/reviewed
    ——ready to run
  2. Develop detail description of test envt and test data
40
Q

Level of detail and associated complexity of work done during test implementation may be influenced by?

A

the detail of the test work products:

Test cases and test conditions

41
Q

TEST EXECUTION starts when?

A

TEST OBJECT is delivered

ENTRY CRITERIA for test execution is satisfied

42
Q

TOOL are in placed for what?

A

Test Management
Defect Tracking (Jira)
Test Execution Automation

43
Q

Test Manager Role during Test Execution

A

MONITOR progress accdg to test plan

CONTROL to guide towards successful conclusion of: MISSION, OBJECTIVES, STRATEGY

Use TRACEABILITY from

  • test results back to test conditions, test basis, objectives
  • from objectives forward to test results
44
Q

Definition of information requirements and methods for collection are part of?

A

TEST PLANNING, MONITORING AND CONTROL

45
Q

WHEN should Test Manager should ensure team members responsible to provide information require in an
ACCURATE
TIMELY MANNER
to facilitate EFFECTIVE EVALUATION AND REPORTING?

A 
During 
TEST ANALYSIS, 
DESIGN, 
IMPLEMENTATION 
EXECUTION
46
Q

Activities when key outputs are captured and either passed to the relevant person or archived

A

TEST CLOSURE

47
Q

4 MAIN GROUPS OF TEST CLOSURE

A
  1. TEST COMPLETION CHECK
  2. TEST ARTIFACTS HANDOVER
  3. LESSONS LEARNED
  4. ARCHIVING RESULTS
48
Q

Test completion Check

A

All test work concluded

Defects fixed or deferred to future release or accepted as permanent restrictions

49
Q

Test artifacts handover

A

user and support the use of the system

Test and environment- MAINTENANCE TESTING

REGRESSION TESTING - MAINTENANCE TEAM

50
Q

LESSONS LEARNED

A

RETROSPECTIVE MEETINGS

51
Q

Lessons Learned

A

User Representation

Estimates

Trends - CAUSE AND EFFECT ANALYSIS

Potential Process Improvement Opportunities

Variances

52
Q

ARCHIVING RESULTS

A

Configuration Mgmt System

53
Q

Task omission reasons

A
  1. Premature reassignment
  2. Dismissal of project team member
  3. Resource or schedule pressure
  4. Team member burnout

QA REVIEW (4 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions