Module 1 - The Test Analysts Tasks in the Test Process Flashcards
Introduction (1.1)
In the ISTQB® Foundation Level syllabus, the test process is described as including the following activities:
Test planning
Test monitoring and control
Test analysis
Test design
Test implementation
Test execution
Test completion
Introduction (1.1)
Determining the appropriate tests, designing and implementing them and then executing them are the primary areas of concentration for the Test Analyst. While it is important to understand the other steps in the test process, the majority of the Test Analyst’s work usually focuses on the following activities:
Test analysis
Test design
Test implementation
Test execution
Intro to the SDLC (1.2)
The overall SDLC should be considered when…
The moment of involvement for the Test Analyst is…
The amount of involvement, time required, information available and expectations can be quite…
The Test Analyst must be aware of…
Defining a test strategy.
Different for the various SDLCs;
Varied as well.
The types of information to supply to other related organizational roles such as:
- Requirements engineering and management - requirements reviews feedback
- Project management - schedule input
- Configuration and change management – results of build verification testing, version control information
- Software development - notifications of defects found
- Software maintenance - reports on defects, defect removal efficiency, and confirmation testing
- Technical support - accurate documentation for workarounds and known issues
- Production of technical documentation (e.g., database design specifications, test environment documentation) - input to these documents as well as technical review of the documents
Intro to the SDLC (1.2)
Test activities must be aligned with the…
the chosen SDLC whose nature may be sequential, iterative, incremental, or a hybrid of these.
Intro to the SDLC (1.2)
In a Sequential V-Model, System test planning occurs…
This will influence…
concurrently with project planning, and test monitoring and control continues until test completion.
The schedule inputs provided by the Test Analyst for project management purposes.
Intro to the SDLC (1.2)
In a Sequential V-Model, System test analysis and design aligns with…
Documents such as the system requirements specification, system and architectural (high-level) design specification, and component (lowlevel) design specification.
Intro to the SDLC (1.2)
In a Sequential V-Model, Implementation of the system test environment might start during…
System design, though the bulk of it typically would occur concurrently with coding and component testing, with work on
system test implementation activities stretching often until just days before the start of system test execution.
Intro to the SDLC (1.2)
In a Sequential V-Model, System test execution begins when…
System test execution continues until…
The entry criteria are met or, if necessary, waived, which typically means that at least component testing and often also component integration testing have met their exit criteria.
The system test exit criteria are met
Intro to the SDLC (1.2)
In a Sequential V-Model, System test completion activities occur…
After the system test exit criteria are met.
Intro to the SDLC (1.2)
Iterative and incremental models may…
For example, an iterative model may…
Test analysis, design, implementation, and execution may…
Not follow the same order of activities and may exclude some activities.
Utilize a reduced set of test activities for each iteration.
Be conducted for each iteration, whereas high-level planning is done at the beginning of the project, and completion tasks are done at the end.
Intro to the SDLC (1.2)
In Agile software development, it is common to use…
There may not be a well-defined…
There is less…
A less formalized process and a much closer working relationship with project stakeholders that allows changes to occur more easily within the project.
Test Analyst role.
Comprehensive test documentation, and communication is shorter and more frequent.
Intro to the SDLC (1.2)
Agile software development involves…
This starts from the…
Reviews may not be…
Involvement is expected to…
Testing from the outset.
Initiation of the product development as the developers perform their initial architecture and design work.
Formalized but are continuous as the software evolves.
Be throughout the project and Test Analyst tasks are expected to be done by the team.
Intro to the SDLC (1.2)
Iterative and incremental models range from…
In such hybrid models, Test Analysts should…
Agile software development, where there is an expectation for change as the customer requirements evolve, to hybrid models, e.g., iterative/incremental development combined with a V-model approach.
Be involved in the planning and design aspects of the sequential activities, and then move to a more interactive role during the iterative/incremental activities.
Intro to the SDLC (1.2)
Whatever the SDLC being used, Test Analysts need to…
Test Analysts provide an…
understand the expectations for involvement as well as the timing of that involvement.
Effective contribution to software quality by adjusting their activities and their moment of involvement to the specific SDLC rather than sticking to a pre-defined role model.
Test Analysis (1.3)
During test planning, the scope of the testing project is defined. During test analysis, Test Analysts use this scope definition to:
- Analyze the test basis
- Identify defects of various types in the test basis
- Identify and prioritize test conditions and features to be tested
- Capture bi-directional traceability between each element of the test basis and the associated test conditions
- Perform tasks associated with risk-based testing (see Chapter 2)
Test Analysis (1.3)
In order for Test Analysts to proceed effectively with test analysis, the following entry criteria should be met:
- There is a body of knowledge (e.g., requirements, user stories) describing the test object that can serve as its test basis (see [ISTQB_FL_SYL] Sections 1.4.2 and 2.2 or a list of other possible sources of test basis).
- This test basis has passed review with reasonable results and has been updated as needed after the review. Note that if high-level test cases are to be defined (see Section 1.4.1), the test basis may not yet need to be fully defined. In Agile software development, this review cycle will be iterative as the user stories are refined at the beginning of each iteration.
- There is an approved budget and schedule available to accomplish the remaining testing tasks for this test object.
Test Analysis (1.3)
Test conditions are typically identified by…
In some situations, where documentation may be old or non-existent, the test conditions may be identified by…
In Agile software development…
Analysis of the test basis in conjunction with the test objectives (as defined in test planning).
Discussion with relevant stakeholders (e.g., in workshops or during iteration planning).
The acceptance criteria, which are defined as part of user stories, are often used as the basis for the test design.
Test Analysis (1.3)
While test conditions are usually specific to the item being tested, there are some standard considerations for the Test Analyst.
1: It is usually advisable to define test conditions at…
Initially, high-level conditions are identified to…
Subsequently, more detailed conditions are identified as…
Using this type of hierarchical approach to defining test conditions can help to…
This approach also allows a Test Analyst to…
2: If product risks have been defined, then the
Differing levels of detail.
Define general targets for testing, such as “functionality of screen x”.
The basis of specific test cases, such as “screen x rejects an account number that is one digit short of the correct length”.
Ensure the coverage is sufficient for the high-level items.
Start working on defining high-level test conditions for user stories that have not yet been refined.
Test conditions that will be necessary to address each product risk should be identified and traced back to that risk item.
Test Analysis (1.3)
The application of test techniques (as identified within the test strategy and/or the test plan) can be helpful in test analysis activities and may be used to support the following objectives:
- Identifying test conditions
- Reducing the likelihood of omitting important test conditions
- Defining more precise and accurate test conditions
Test Analysis (1.3)
After the test conditions have been identified and refined:
Review of these conditions with the stakeholders can be conducted to ensure the requirements are clearly understood and that testing is aligned with the goals of the project.
Test Analysis (1.3)
At the conclusion of the test analysis activities for a given area (e.g., a specific function), the Test Analyst should know…
What specific tests must be designed for that area.
