РОМАН ШАЙДА "How to build your own Testing Strategy"

•Download as PPTX, PDF•

0 likes•196 views

The document provides guidance on how to build a testing strategy. It recommends starting with a high-level overview and then designing a test plan based on criteria like project roadmap, acceptance criteria, environments, and risk analysis. It also recommends defining different types of testing. The testing strategy should then create test suites, outline test executions and processes, schedule meetings, define a task lifecycle, and process for submitting defects. The key components of an effective testing strategy are test suite creation, test executions, processes, meetings, task management, defect tracking, and integration with continuous integration.

Education

- snowboarder
- music lover
- traveller
- gamer
- and a lot more)

Life in Norway: “There's no such thing as bad
weather, only bad clothes”

Test plan should be design
based on the following criterias:
1.
2.
3.
4.
5.
6.
7.
8.

Test plan should be design
based on the following criterias:
1. Project Roadmap
2.
3.
4.
5.
6.
7.
8.

Test plan should be design
based on the following criterias:
1. Project Roadmap
2. Resource Planning / Budget
3.
4.
5.
6.
7.
8.

Test plan should be design
based on the following criterias:
1. Project Roadmap
2. Resource Planning / Budget
3. Acceptance Criteria
4.
5.
6.
7.
8.

Test plan should be design
based on the following criterias:
1. Project Roadmap
2. Resource Planning / Budget
3. Acceptance Criteria
4. Most commonly used environments
5.
6.
7.
8.

2. Resource Planning / Budget
(manual testing / automated testing)

3. Gherkin DSL = Acceptance Criteria
Wait, what?

3. Gherkin DSL = Acceptance Criteria
(UX prototypes is a good plus)

4. Most commonly used environments
(OS/Browsers/Mobile devices)

7. Definition of testing types
Types of testing should be defined based on project-specific
resources/budget/roadmap/AC/environment analysis:

7. Definition of testing types
Types of testing should be defined based on project-specific
resources/budget/roadmap/AC/environment analysis:
● Unit Testing

Okay…Now we are ready to create a Test
Strategy!

What is the Test Strategy?
Test Strategy is the document which describes
how to deal with the Test Plan

What is the Test Strategy?
Test Strategy is the document which describes
how to deal with the Test Plan
© на хлопський розум

Based on the “preparation phase” and Test Plan
design we can build our Testing Strategy!

Main Components of a Test Strategy are:
1. Test Suites/Sets creation

Main Components of a Test Strategy are:
1. Test Suites/Sets creation
2. Test Executions

Main Components of a Test Strategy are:
1. Test Suites/Sets creation
2. Test Executions
3. Processes

Main Components of a Test Strategy are:
1. Test Suites/Sets creation
2. Test Executions
3. Processes
4. Meetings

Main Components of a Test Strategy are:
1. Test Suites/Sets creation
2. Test Executions
3. Processes
4. Meetings
5. Tasks lifecycle

Main Components of a Test Strategy are:
1. Test Suites/Sets creation
2. Test Executions
3. Processes
4. Meetings
5. Tasks lifecycle
6. Defects update and submission

4. Meetings
- - Stand-Up Meeting (15 minutes, Every Day)
- - Grooming (Refinement Session, 0.5 to 1 hours, 1-2 Times per Week)
- - Sprint Review Meeting at the End of the Sprint (2-4 Hours)
- - Sprint Planning (2-4 Hours)
- - Retrospective Meeting at the End of the Sprint (1 Hour)

5. Tasks lifecycle
- Levels:
Epic -> Story -> Task/Bug/Feature/Sub task

5. Tasks lifecycle
- Levels:
Epic -> Story -> Task/Bug/Feature/Sub task
- - Dev team Steps - QA team Steps - DevOps Steps

6. Defects update and submission
- Description:
- - Environment: test/stage/prod
- - Country(optional)
- - Language(optional)
- - Browser/Device: chrome/firefox/ie/mobile device
- - Browser/Device version: chrome/firefox/ie/mobile device versions
- - Build version: Build version
- Steps to reproduce:
- should contain detailed steps how to reproduce the bug
- Actual result: -//-
- Expected result: -//-
- Notes:(optional)

7. CI processes
JIRA fields:
- Affects Version/s:
- Fix Version/s:
Example:
It should return the branch, date, release number and environment info:
BRANCH:
Development
RELEASE:
SPRINT-1
Date of latest build:
DATE:
Wed May 9 10:46:45 CEST 2018

Q/A ?
Contact:
dimencionr@gmail.com
https://www.facebook.com/roman.shayda
https://linkedin.com/in/romanshayda/
https://www.youtube.com/user/dimencionrider
https://github.com/dimencionrider

Meetup TestingUy | Montevideo, Uruguay | 1st August 2017 Abstract This presentation is about a testing strategy to automate the Viewer, one of the core features of the product under test, a multi-platform UI prototyping tool (mainly) for Interaction Designers, in the context of a cross-functional team fully dedicated to developing a single product. Claudia will also share what they've learnt as a team from the testing perspective and how the tester role in the team has changed during this journey. Duration: 45 minutes

Meetup TestingUY 2016: Adopting testing in a cross-functional team

Claudia Badell

ISTQB / ISEB Foundation Exam Practice - 2

Yogindernath Gupta

The document discusses various topics related to software testing including: 1. It introduces different levels of testing in the software development lifecycle like component testing, integration testing, system testing and acceptance testing. 2. It discusses the importance of early test design and planning and its benefits like reducing costs and improving quality. 3. It provides examples of how not planning tests properly can increase costs due to bugs found late in the process, and outlines the typical costs involved in fixing bugs at different stages.

ISTQB, ISEB Lecture Notes- 2

onsoftwaretest

This document discusses various types of software testing performed at different stages of the software development lifecycle. It describes component testing, integration testing, system testing, and acceptance testing. Component testing involves testing individual program units in isolation. Integration testing combines components and tests their interactions, starting small and building up. System testing evaluates the integrated system against functional and non-functional requirements. Acceptance testing confirms the system meets stakeholder needs.

Mobile Testing Capability

BusinessIntelligenze

Mobile application testing requires different approaches than software testing due to factors like diverse devices, platforms, and content types. The document outlines a 7-step approach to testing that includes planning, specification, execution, and reporting. It also discusses security measures and the different testing needs for various mobile content types such as web apps, SMS apps, and native apps.

ISTQBCH2.ppt

RppsKumar1

ISTQBCH2.ppt

ghkadous

ISTQB Foundation - Chapter 2

Chandukar

The document discusses various types and stages of software testing in the software development lifecycle, including: 1. Component testing, the lowest level of testing done in isolation on individual software modules. 2. Integration testing in small increments to test communication between components and non-functional aspects. 3. System testing to test functional and non-functional requirements at the full system level, often done by an independent test group. 4. The document provides details on planning, techniques, and considerations for each type of testing in the software development and integration process.

The document discusses the fundamental test process which includes test planning and control, test analysis and design, test implementation and execution, evaluating exit criteria and reporting, and test closure activities. It provides details on the major tasks involved in each part of the test process. These include determining test objectives and approach, developing test cases and suites, executing tests, logging results, and evaluating whether exit criteria are met. The purpose is to lay out the basic steps involved in software testing from the initial planning through closing out the testing activities.

Volodymyr Prymakov and Vlada Benyukh Detailed manual estimation approach for ...

Ievgenii Katsan

This document provides guidance on conducting manual test estimation for the pre-sale phase of a project. It discusses factors to consider like requirements, environments, and complexity. Main activities to estimate include requirements review, test design, execution, and bug handling. Regression is calculated based on sprint count, tested functionality percentage, and environments. Risks like changing requirements and infrastructure issues are accounted for with multipliers. A demo is provided of estimating a real project involving calculations, environments, and risks. Statistics on past projects estimated duration and team size are also included.

How to create a 'Master Test Plan'

PractiTest

Continuous testing in agile projects 2015

Fabricio Epaminondas

This document discusses continuous testing in an agile environment. It defines continuous testing as testing throughout the development process to identify bugs early. It explains that continuous testing helps control side effects, avoid defects, support multiple environments, get fast results, anticipate risks, and create reliable processes. The document provides an overview of how continuous testing works, including test environments, data management, automatic deployment, and test automation. It also discusses creating a continuous testing project, the agile test process, and how to implement effective continuous testing to improve quality and business value.

STLC-ppt-1.pptx

sangeeta607494

The document describes the Software Testing Life Cycle (STLC) which consists of 6 phases to ensure software quality: 1) Requirement Analysis where testable requirements are identified, 2) Test Planning which describes the testing strategy and plan, 3) Test Case Development where test cases and data are created, 4) Test Environment Setup where testing conditions are decided, 5) Test Execution where testing is performed based on test plans and cases, and 6) Test Closure Activities which ensure testing is complete and artifacts are handed over. The STLC uses entry and exit criteria to determine when a phase can begin or end.

stlc

transformtoit

The document provides an overview of the software testing life cycle (STLC) which includes test planning, test development, test execution, result analysis, defect management, and summarized reports. It then describes each phase in more detail, outlining key activities, participants, and deliverables. For example, test planning involves preparing test strategies and plans, estimating effort, and identifying risks. Test development consists of writing test cases and scripts, setting up environments, and reviewing test artifacts. The document also defines common testing terms like test plans, test cases, defect priority and severity levels.

Test planning & estimation

Leslie Smart

Test planning involves defining the scope, objectives, and activities for testing a project. It is done early in the project and produces a master test plan. Key activities include identifying what needs testing, assigning roles and resources, and defining entry and exit criteria. Estimating test effort can be done using metrics from past projects or by eliciting estimates from subject matter experts. Product characteristics, development processes, and expected test outcomes all impact the level of effort required for testing.

360logica_Testing_center_of_excellence

guestf2e1db

Stlc ppt

Bhavik Modi

The document outlines the key phases of the Software Testing Life Cycle (STLC) process. It describes 6 phases: 1) Requirement Analysis/Review to understand requirements, 2) Test Planning to develop the test plan, 3) Test Designing to create test cases and scripts, 4) Test Environment Setup to prepare the test environment, 5) Test Execution to run the test cases and report bugs, and 6) Test Closure to finalize testing and complete documentation. The goal of STLC is to systematically test software through a planned process to improve quality.

Software testing interview Q&A – Part 2

Khoa Bui

stlc

transformtoit

Chapter 1 Fundamental of Testing

Siti Deny Nadiroha

In this chapter, we will introduce you to the fundamentals of testing: why testing is needed; its limitations, objectives and purpose; the principles behind testing; the process that testers follow; and some of the psychological factors that testers must consider in their work. By reading this chapter you'll gain an understanding of the fundamentals of testing and be able to describe those fundamentals.

Istqb foundation level day 1

Shuchi Singla AKT,SPC4,PMI-ACP,ITIL(F),CP-AAT

The document provides an overview of the agenda and content for Day 1 of an ISTQB Foundation Level training course. It begins with an introduction to ISTQB, including what it is, its purpose, and certification levels. It then outlines the agenda for Day 1, which includes introductions to ISTQB, principles of testing, testing throughout the software development lifecycle, static testing techniques, and tool support for testing. The document provides details on each of these topics, such as definitions of testing, principles of testing, software development models, testing levels, types of testing, and examples of static testing techniques.

End to End Test Management Test Strategy Estimation and Metrics Workshop

QAAgility Technologies

This document outlines the agenda for a two-day Test Management Workshop. Day 1 covers test strategy and planning, understanding the development methodology and its impact, test types like CIT and UAT, test automation, non-functional testing, and identifying and managing project risks. Exercises are included. Day 2 covers test estimation fundamentals and techniques like NTC and WBS, understanding scheduling, and a final exercise preparing a full test strategy document. An optional third day could cover additional estimation techniques and test metrics. The workshop aims to provide guidance on formulating a test strategy and plan.

2 to 3 days End to End Test Management Test Strategy Estimation and Metrics W...

Ashish Mishra

This document outlines the agenda for a two-day test management workshop. Day 1 covers test strategy and planning, including understanding scope, processes, development methodologies, and test types. It also covers automation, non-functional testing, risks, and roles. Day 2 focuses on test estimation techniques like NTC and WBS, as well as scheduling. Exercises are included for various topics. An optional third day could cover additional estimation techniques and test metrics. The goal is to help participants develop an end-to-end test strategy.

Performance testing reference model

Eduards Salnikovs

Bab i fundamental of testing

Riauly Putra

The document summarizes the fundamental test process which consists of 5 basic steps: 1) planning and control which involves determining test objectives, approach, and resources; 2) analysis and design which involves reviewing requirements, identifying test conditions, and designing test cases; 3) implementation which involves developing and prioritizing test cases and creating test suites; 4) execution which involves executing test cases and logging results; 5) evaluating exit criteria and reporting which involves checking test logs and writing a summary report. The fundamental test process is used for dynamic testing but can also be applied to reviews. Testing is done to determine if a system is suitable for use.

Bab i fundamental of testing (yoga)

sidjdhdjsks

The document summarizes the fundamental test activities from planning to closure. It describes the main tasks for each stage of testing including: planning and control, analysis and design, implementation and execution, evaluating exit criteria and reporting, and test closure activities. For each stage, it lists the major tasks in the typical order they are performed such as determining test objectives, designing test cases, executing tests, analyzing results, and finalizing test documentation.

chapter-no-4-test-management fudhg ddh j

AmitDeshai

Testing documents

Hari Tiru

1. The document describes various testing documents created at different levels of a project testing process. Test policy, strategy, and methodology documents are created at higher levels, while test plans, cases, procedures, scripts, and reports are created at the project level. 2. It provides details on different testing documents - test policy defines testing objectives, test strategy defines the testing approach, and test methodology provides the testing approach for a specific project. It also describes how test plans are created, test cases are designed based on requirements, and the different levels of test execution. 3. The key testing documents created are test policy, strategy, methodology, plan, cases, procedures, scripts, and reports. Test cases are designed based

ОЛЕКСА МАЩИЦЬ «Пора валити! Або коли компанія тобі більше не друг»

РОМАН ШАЙДА "How to build your own Testing Strategy"

Recommended

Recommended

More Related Content

Similar to РОМАН ШАЙДА "How to build your own Testing Strategy"

Similar to РОМАН ШАЙДА "How to build your own Testing Strategy" (20)

More from QADay

More from QADay (20)

Recently uploaded

Recently uploaded (20)

РОМАН ШАЙДА "How to build your own Testing Strategy"