Software Testing Foundation: Based on ISTQB Standards (Chapter 1: Fundamentals of Testing)

0.0(0)
studied byStudied by 3 people
0.0(0)
full-widthCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/86

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

87 Terms

1
New cards

ISTQB

International Software Testing Qualifications Board

2
New cards

November 2002

About ISTQB

Founded, ____________________

3
New cards

Belgium

About ISTQB

Not-for-profit association legally registered in ____________________.

4
New cards

ISTQB® Certified Tester

About ISTQB

Has defined the "__________________________" scheme that has become the worldwide leader in the certification of competences in software testing.

5
New cards

Causes of Software Failures

-Time Pressure

-Complex Codes

-Complex Infrastructure

-Changing Technologies

-Many System Interactions

6
New cards

Error

Mistake

7
New cards

Defect

Fault, bug

8
New cards

Defect

A problem in the program code (or related work product)

9
New cards

Failure

Defects + Environmental Conditions

10
New cards

Failure

System failing to do what it should do or doing something that it should not do

11
New cards

risk

Role of Testing in Software Development, Maintenance and Operations

Benefits of rigorous testing of systems and documentation

Helps reduce the ___________ of problems occurring in delivered systems

12
New cards

defects

Role of Testing in Software Development, Maintenance and Operations

Benefits of rigorous testing of systems and documentation

Contributes to the quality of the software systems if ___________________ are corrected before the system is released

13
New cards

Industry-specific standards

Role of Testing in Software Development, Maintenance and Operations

Benefits of rigorous testing of systems and documentation

May be required to meet

○ Contractual requirements ○ Legal requirements

○ _________________________________

14
New cards

35% & 80%

Role of Testing in Software Development, Maintenance and Operations

Benefits of rigorous testing of systems and documentation

On average, testing user ______________ of the IT budget, but can use ___________ on safety critical systems

15
New cards

functional and non-functional

Testing and Quality

Testing can help:

Measure the quality of the software in terms of defects found, for both _____________________ and _____________________ software requirements and characteristics

16
New cards

confidence & Few defects

Testing and Quality

Testing can help:

Can give ______________in the quality of the software if it finds few or no defects

○ __________________ = confidence in the quality increases

○ Reduces overall level of risk when a properly designed test have passed

17
New cards

defects

Testing and Quality

Testing can help:

When testing finds _______________, the quality of the software increases when those defects are fixed.

18
New cards

Testing

Testing and Quality

Testing can help:

__________________ should be integrated as one of the quality assurance activities

19
New cards

confidence

Testing and Quality

Quality Assurance

Part of quality management focused on providing ________________ that quality requirements will be fulfilled. (ISTQB definition)

20
New cards

root causes of defects

Testing and Quality

Quality Assurance

Lessons should be learned from previous projects. Understanding the ______________________ found in other project, processes can be improved, which should PREVENT those defects from reoccurring, therefore improve the quality of future systems.

21
New cards

Testing

Testing and Quality

Quality Assurance

_________________ is one of the Quality Assurance Activities

22
New cards

Level of Risk

How Much Testing is Enough?

Deciding how much testing is enough should take account the level of risk and project constraints

- Technical

- Safety

- Business

23
New cards

Project Constraints

How Much Testing is Enough?

Deciding how much testing is enough should take account the level of risk and project constraints

- Time

- Budget

- People

24
New cards

sufficient information

How Much Testing is Enough?

Deciding how much testing is enough should take account the level of risk and project constraints

Testing should provide _______________________ to stakeholders to make informed decisions about the release of the software or system being tested, for the next deployment step or handover to customers

25
New cards

Reviews

Test Objectives across the Life Cycle

Of documents (e.g. requirements) and the identification and resolution of issues helps to prevent the defects appearing in the code

26
New cards

Acceptance Testing

Test Objectives across the Life Cycle

To confirm that the system works as expected, and to gain confidence that it has met the requirements

27
New cards

Maintenance Testing

Test Objectives across the Life Cycle

Includes testing that no new defects have been introduced during the implementation of the changes

28
New cards

Quality Evaluation

Test Objectives across the Life Cycle

To assess the quality of the software - to give

information to stakeholders of the risks of

releasing the system at a given time

29
New cards

Operational Testing

Test Objectives across the Life Cycle

To assess ongoing system characteristics such as reliability or availability

30
New cards

Development Testing

Test Objectives across the Life Cycle

To cause as many failures as possible so that the defects in the software are identified and can be fixed

31
New cards

Dynamic Testing

Tester

___________________ reveals failures

32
New cards

Re-testing

Tester

____________________ ensures that the fix really resolves the failure

33
New cards

Debugging

Developer

_________________ locates, analyses and removes the cause of the failure (defects)

34
New cards

test execution

Fundamental Test Process

The most visible part of testing is ___________________. But to be effective and efficient, test plans should also include time to be spent on planning the tests, designing test cases, preparing for execution and evaluating results.

35
New cards

scope and risks

Test Planning and Control

Determining the ______________ and ______________ and identifying the objectives of testing

36
New cards

Defining

Test Planning and Control

________________ the overall approach of testing, including the definition of the test levels and entry and exit criteria

37
New cards

testing activities

Test Planning and Control

Integrating and coordinating the _________________ into the software life cycle activities (acquisition, supply, development, operation and maintenance)

38
New cards

decisions

Test Planning and Control

Making ________________ about what to test, what roles will perform the test activities, how the test activities should be done, and how the test results will be evaluated

39
New cards

Scheduling

Test Planning and Control

_____________________ test analysis and design activities, test implementation, execution and evaluation

40
New cards

resources

Test Planning and Control

Assigning ________________ for the different activities defined

41
New cards

amount

Test Planning and Control

Defining the______________, level of detail, structure and templates for the test documentation

42
New cards

metrics

Test Planning and Control

Selecting ________________ for monitoring and controlling test preparation and execution, defect resolution and risk issues

43
New cards

reproducible test

Test Planning and Control

Setting the level of detail for test procedures in order to provide enough information to support ________________________ preparation and execution

44
New cards

test monitoring

Test Planning and Control

Making decisions based on information from _______________________

45
New cards

Re-prioritizing

Test Planning and Control

_______________________ tests when an identified risk occurs (e.g. software delivered late)

46
New cards

test environment

Test Planning and Control

Changing the test schedule due to availability or unavailability of a _______________________

47
New cards

entry criterion

Test Planning and Control

Setting an ____________________ requiring fixes to have been re-tested (confirmation tested) by a developer before accepting them into a build

48
New cards

test basis

Test Analysis and Design

Reviewing the ___________________ (such as requirements, software integrity level (risk level), risk analysis reports, architecture, design, interface specifications)

49
New cards

testability

Test Analysis and Design

Evaluating ___________________ of the test basis and test objects

50
New cards

test conditions

Test Analysis and Design

Identifying and prioritizing _____________________ based on analysis of test items, the specification, behavior and structure of the software

51
New cards

high level

Test Analysis and Design

Designing and prioritizing ____________________ test cases

52
New cards

test data

Test Analysis and Design

Identifying necessary ___________________ to support the test conditions and test cases

53
New cards

test environment

Test Analysis and Design

Designing the _____________________ setup and identifying any required infrastructure and tools

54
New cards

bi-directional traceability

Test Analysis and Design

Creating _____________________ between test basis and test cases

55
New cards

test cases

Test Implementation and Execution

Finalizing, implementing and prioritizing ) ________________ (including the identification of test data)

56
New cards

test procedures

Test Implementation and Execution

Developing and prioritizing ___________________, creating test data and, optionally, preparing test harnesses and writing automated test scripts

57
New cards

test suites

Test Implementation and Execution

Creating ________________ from the test procedures for efficient test execution

58
New cards

test environment

Test Implementation and Execution

Verifying that the ____________________ has been set up correctly

59
New cards

test basis and test cases

Test Implementation and Execution

Verifying and updating bi-directional traceability between the _____________________ and _____________________

60
New cards

test procedures

Test Implementation and Execution

Executing _____________________ either manually or by using test execution tools, according to the planned sequence

61
New cards

test execution

Test Implementation and Execution

Logging the outcome of _____________________ and recording the identities and versions of the software under test, test tools and testware

62
New cards

expected results

Test Implementation and Execution

Comparing actual results with ______________________

63
New cards

discrepancies

Test Implementation and Execution

Reporting ________________ as incidents and analyzing them in order to establish their cause (e.g. a defect in the code, in specified test data, in the test document, or a mistake in the way the test was executed)

64
New cards

test activities

Test Implementation and Execution

Repeating ____________________ as a result of action taken for each discrepancy, for example, re-execution of a test that previously failed in order to confirm a fix (confirmation testing), execution of a corrected test and/or execution of tests in order to ensure that defects have not been introduced in unchanged areas of the software or that defect fixing did not uncover other defects (regression testing)

65
New cards

test logs

Evaluation Exit Criteria and Reporting

Checking ________________ against the exit criteria specified in test planning

66
New cards

exit criteria

Evaluation Exit Criteria and Reporting

Assessing if more tests are needed or if the __________________ specified should be changed

67
New cards

test summary

Evaluation Exit Criteria and Reporting

Writing a _________________ report for stakeholders

68
New cards

planned deliverables

Test Closure Activities

Checking which ____________________ have been delivered

69
New cards

incident reports

Test Closure Activities

Closing __________________ or raising change records for any that remain open

70
New cards

acceptance

Test Closure Activities

Documenting the __________________ of the system

71
New cards

archiving testware

Test Closure Activities

Finalizing and ____________________, the test environment and the test infrastructure for later reuse

72
New cards

maintenance organization

Test Closure Activities

Handing over the testware to the _______________________

73
New cards

changes needed

Test Closure Activities

Analyzing lessons learned to determine ________________________ for future releases and projects

74
New cards

test maturity

Test Closure Activities

Using the information gathered to improve ______________________

75
New cards

People are driven by objectives set by management and other stakeholders

Psychological Factors Influencing Testing

E.g. "find defects" and "confirm software works"

76
New cards

Testing is often seen as a destructive activity as it identifies failures

Psychological Factors Influencing Testing

However, to find failures requires curiosity, professional pessimism, a critical eye, attention to detail, good communication with development peers, and experience on which to base the error guessing

77
New cards

Communication of defects in a constructive way

Psychological Factors Influencing Testing

Bad feelings between the tester and analysts, designers and developers can be avoided

78
New cards

Testers (and Reviewers) have a different mindset from developers

Psychological Factors Influencing Testing

○ A certain degree of independence (avoiding author bias) often makes the tester more effective at finding defects and failures ○ They can focus in finding Defects

○ They provide an independent view as trained, professional testing resources

79
New cards

Independence makes testers more effective

Psychological Factors Influencing Testing

however developers' familiarity with the software is also useful - they can efficiently find many defects in their own code

80
New cards

PUBLIC

Code of Ethics

Certified software testers shall act consistently with the public interest

81
New cards

CLIENT AND EMPLOYER

Code of Ethics

Certified software testers shall act in a manner that is in the best interests of their client and employer, consistent with the public interest

82
New cards

PRODUCT

Code of Ethics

Certified software testers shall ensure that the deliverables they provide (on the products and systems they test) meet the highest professional standards possible

83
New cards

JUDGMENT

Code of Ethics

Certified software testers shall maintain integrity and independence in their professional judgment

84
New cards

MANAGEMENT

Code of Ethics

Certified software test managers and leaders shall subscribe to and promote an ethical approach to the management of software testing

85
New cards

PROFESSION

Code of Ethics

Certified software testers shall advance the integrity and reputation of the profession consistent with the public interest

86
New cards

COLLEAGUES

Code of Ethics

Certified software testers shall be fair to and supportive of their colleagues, and promote cooperation with software developers

87
New cards

SELF

Code of Ethics

Certified software testers shall participate in lifelong learning regarding the practice of their profession and shall promote an ethical approach to the practice of the profession