This document discusses risk in software testing and risk management. It defines risk as a potential problem that could endanger project objectives. There are three main types of risk: product risks relating to the software itself, project risks relating to how work is carried out, and business risks that could cause financial loss. Testing aims to manage risk through identification, analysis, mitigation, and monitoring. Risk analysis involves determining the impact and likelihood of risks, while mitigation builds tests to address risks.
Олександр Струков “QA skills keeping it up to date” Dakiry
This document discusses QA skills and keeping skills up to date. It provides an overview of the history of QA, important skills to start with including both hard skills like testing types and mobile testing, and soft skills like communication. It also outlines a range of additional skills in areas like automation, security, and programming that QA professionals should aim to develop. It emphasizes the importance of continuous learning and prioritizing skill development over time, referencing Josh Kaufman's concept of focusing on a new skill for 20 hours to achieve competency.
Альона Тудан “World of bugs: let’s find together”Dakiry
The document categorizes types of bugs into several groups: documents, UI, logical, technical, localized, mapping, and combined. It provides examples of conditions and results for each group. The summary concludes that bugs can appear anywhere, their presence may not be clearly understood, and exhaustive testing is impossible.
Bohdana Muzyka “GUI and Usability Testing: Becoming User Advocate”Dakiry
The document discusses usability testing and the role of a user advocate. It defines graphical user interfaces (GUIs) and usability, explaining why they are important. A user advocate represents the user's point of view, ensuring their needs are met. The user advocate gets involved early, tests from the user perspective, and bridges development and users. Challenges for advocates include lack of user information and unaddressed user needs. Common GUI challenges for users are scrolling, drag and drop, window management, and more. The document outlines laws of user experience like clarity, preferred actions, context, and feedback to improve usability.
This document discusses risk in software testing and risk management. It defines risk as a potential problem that could endanger project objectives. There are three main types of risk: product risks relating to the software itself, project risks relating to how work is carried out, and business risks that could cause financial loss. Testing aims to manage risk through identification, analysis, mitigation, and monitoring. Risk analysis involves determining the impact and likelihood of risks, while mitigation builds tests to address risks.
Олександр Струков “QA skills keeping it up to date” Dakiry
This document discusses QA skills and keeping skills up to date. It provides an overview of the history of QA, important skills to start with including both hard skills like testing types and mobile testing, and soft skills like communication. It also outlines a range of additional skills in areas like automation, security, and programming that QA professionals should aim to develop. It emphasizes the importance of continuous learning and prioritizing skill development over time, referencing Josh Kaufman's concept of focusing on a new skill for 20 hours to achieve competency.
Альона Тудан “World of bugs: let’s find together”Dakiry
The document categorizes types of bugs into several groups: documents, UI, logical, technical, localized, mapping, and combined. It provides examples of conditions and results for each group. The summary concludes that bugs can appear anywhere, their presence may not be clearly understood, and exhaustive testing is impossible.
Bohdana Muzyka “GUI and Usability Testing: Becoming User Advocate”Dakiry
The document discusses usability testing and the role of a user advocate. It defines graphical user interfaces (GUIs) and usability, explaining why they are important. A user advocate represents the user's point of view, ensuring their needs are met. The user advocate gets involved early, tests from the user perspective, and bridges development and users. Challenges for advocates include lack of user information and unaddressed user needs. Common GUI challenges for users are scrolling, drag and drop, window management, and more. The document outlines laws of user experience like clarity, preferred actions, context, and feedback to improve usability.
Генерація лідів - основна щоденна активність сучасного маркетолога, і це є далеко не проста штука. В пошуках нових методів генерації маркетологи зачасту роблять багато помилок, що є нормально, але є помилки, які коштують компаніям дуже дорого.
Анна Косарєва "Чому жінки почали обирати інженерні спеціальності"Dakiry
The document discusses various topics in a disjointed manner including greetings in different languages, exceptions, disagreements, gender roles, mathematics, cash registers, unemployment rates from 2011-2015, job roles for recruiting, web design, and testing. It jumps between unrelated words, phrases, and data without any clear overall theme or narrative to tie the information together.
Тетяна Голубєва "Fix yourself and world will be fixed around you"Dakiry
This document discusses how fixing yourself can lead to fixing the world around you. It touches on topics like the differences between men and women, goals versus how to achieve them, focusing on one thing at a time, believing in yourself, and balancing rationality with emotions. The overall message is that improving yourself is key to improving your circumstances and relationships.
Dakiry social night _daniil leping_startup.-lottery-or-business-Dakiry
This document discusses reasons why startups often fail and provides perspectives on entrepreneurship. It lists sources that identify 5-20 common reasons for startup failure, including issues with the market, business model, management team, running out of cash, and product problems. The document then discusses the realities entrepreneurs often face, such as dealing with ego and wanting validation. It emphasizes the importance of professionalism for experienced entrepreneurs and that success comes despite, not due to, challenges that arise along the way.
DaKiRy_PMWeekend2016_Андрій Рифяк "Product development for Enterprises: Short...Dakiry
This document provides guidance on product development for enterprises. It discusses business models for product development versus outsourcing. It also outlines key considerations for the product itself including features, architecture, and development process. Additional topics covered include product support, documentation, versioning, marketing, budgeting, integration with other systems, security, and lessons learned. The overall message is that product development requires planning across many areas to balance expectations with reality.
DaKiRY_BAQ2016_QADay_Яків Крамаренко "Автоматизація - це просто! (C#)"Dakiry
This document discusses automation testing and provides tips for getting started with test automation. It recommends starting with end-to-end smoke tests using an easy language and tools. Specific suggestions include using C# with the nSelene library or Java with Selenide. The document emphasizes that automation is a tool to help testers do their work more efficiently, and that one can start automating even without manual testing experience if they have support and learn the basics.
DaKiRy_PMStandUp_Євген Філяк “What Product Managers do in Ukrainian IT compan...Dakiry
The document discusses the role of product managers (PdMs) in Ukrainian IT companies. It notes that PdMs are responsible for identifying market pricing, buyers and users, launch plans, prioritizing features, orchestrating product development, creating roadmaps, and owning budgets. Charts show increasing vacancies for PdMs from 2013-2016. PdMs look outside at the market while BAs look inside at requirements. The roles of PdMs are compared to those in marketing, sales, and pricing. While some CEOs see PdMs as important for growth, others argue they are not needed for outsourcing companies.
DaKiRy_QAStandUp_Наталія Коваль "Testing tools and tips"Dakiry
The document provides tips and recommendations for various tools that can be used at different stages of the testing process, including project management tools, test management tools, tools for executing tests, cross-browser testing tools, debugging and automation tools, and security verification tools. The document encourages searching for additional useful tips and tools and asks which other tools readers would recommend.
DaKiRy_PMWeekend2016_Валентин Будкін "Мітинги в Scrum - the Good, the Bad and...Dakiry
The document discusses various Scrum meetings and provides classifications of "The Good, The Bad, and The Ugly" for each meeting. It summarizes the Daily Standup meeting as having a timebox of 15 minutes where the team updates each other on work, which is good, but can be bad if driven or includes silent members or micromanaging. It also notes implementation talk and using the improvement board as ugly aspects.
Що ми будемо робити на вебінарі? Ми розберемо такі явища
✅ як нарцистичний розлад особистості,
✅ грандіозний нарцисизм,
✅ газлайтинг,
✅ знецінення,
✅ гойдалки вина-лють-вина,
✅ нарцистичне розширення,
✅ бомбардування любов’ю,
✅ мімікрування,
✅ створення ілюзорного майбутнього,
✅ контроль,
✅ спалахи гніву,
✅ вгадування майбутнього,
✅ вибір перебором, трошки хлібчика, щоб не подох,
✅ відштовхування/кидання/блокування,
✅ покарання мовчанням.
МАНІПУЛЯЦІЇ: ХТО КОГО І ДЛЯ ЧОГО? - Інна ТіторенкоDakiry
ВЕБІНАР: "МАНІПУЛЯЦІЇ: ХТО КОГО І ДЛЯ ЧОГО?":
Що таке маніпуляції?
Які бувають види маніпуляції, як їх відрізнити?
Хто і чому маніпулює?
Чи добре чи погано маніпулювати?
І звичайно, як їм протистояти?
Під час доповіді поговоримо про участь бізнес-аналітиків і розкриємо основні складові discovery workshop:
- Організація. Коли проведення воркшопу, окрім стартової фази, є максимально ефективним?
- Підготовка. Як почати з нічого і якісно підготуватись до воркшопу у стислі терміни?
- Проведення: Workshop Do’s and Don’ts. Приклади технік і вправ, а також приблизний план самого воркшопу.
- Оформлення кінцевих результатів або презентації, що запам’ятовуються
Генерація лідів - основна щоденна активність сучасного маркетолога, і це є далеко не проста штука. В пошуках нових методів генерації маркетологи зачасту роблять багато помилок, що є нормально, але є помилки, які коштують компаніям дуже дорого.
Анна Косарєва "Чому жінки почали обирати інженерні спеціальності"Dakiry
The document discusses various topics in a disjointed manner including greetings in different languages, exceptions, disagreements, gender roles, mathematics, cash registers, unemployment rates from 2011-2015, job roles for recruiting, web design, and testing. It jumps between unrelated words, phrases, and data without any clear overall theme or narrative to tie the information together.
Тетяна Голубєва "Fix yourself and world will be fixed around you"Dakiry
This document discusses how fixing yourself can lead to fixing the world around you. It touches on topics like the differences between men and women, goals versus how to achieve them, focusing on one thing at a time, believing in yourself, and balancing rationality with emotions. The overall message is that improving yourself is key to improving your circumstances and relationships.
Dakiry social night _daniil leping_startup.-lottery-or-business-Dakiry
This document discusses reasons why startups often fail and provides perspectives on entrepreneurship. It lists sources that identify 5-20 common reasons for startup failure, including issues with the market, business model, management team, running out of cash, and product problems. The document then discusses the realities entrepreneurs often face, such as dealing with ego and wanting validation. It emphasizes the importance of professionalism for experienced entrepreneurs and that success comes despite, not due to, challenges that arise along the way.
DaKiRy_PMWeekend2016_Андрій Рифяк "Product development for Enterprises: Short...Dakiry
This document provides guidance on product development for enterprises. It discusses business models for product development versus outsourcing. It also outlines key considerations for the product itself including features, architecture, and development process. Additional topics covered include product support, documentation, versioning, marketing, budgeting, integration with other systems, security, and lessons learned. The overall message is that product development requires planning across many areas to balance expectations with reality.
DaKiRY_BAQ2016_QADay_Яків Крамаренко "Автоматизація - це просто! (C#)"Dakiry
This document discusses automation testing and provides tips for getting started with test automation. It recommends starting with end-to-end smoke tests using an easy language and tools. Specific suggestions include using C# with the nSelene library or Java with Selenide. The document emphasizes that automation is a tool to help testers do their work more efficiently, and that one can start automating even without manual testing experience if they have support and learn the basics.
DaKiRy_PMStandUp_Євген Філяк “What Product Managers do in Ukrainian IT compan...Dakiry
The document discusses the role of product managers (PdMs) in Ukrainian IT companies. It notes that PdMs are responsible for identifying market pricing, buyers and users, launch plans, prioritizing features, orchestrating product development, creating roadmaps, and owning budgets. Charts show increasing vacancies for PdMs from 2013-2016. PdMs look outside at the market while BAs look inside at requirements. The roles of PdMs are compared to those in marketing, sales, and pricing. While some CEOs see PdMs as important for growth, others argue they are not needed for outsourcing companies.
DaKiRy_QAStandUp_Наталія Коваль "Testing tools and tips"Dakiry
The document provides tips and recommendations for various tools that can be used at different stages of the testing process, including project management tools, test management tools, tools for executing tests, cross-browser testing tools, debugging and automation tools, and security verification tools. The document encourages searching for additional useful tips and tools and asks which other tools readers would recommend.
DaKiRy_PMWeekend2016_Валентин Будкін "Мітинги в Scrum - the Good, the Bad and...Dakiry
The document discusses various Scrum meetings and provides classifications of "The Good, The Bad, and The Ugly" for each meeting. It summarizes the Daily Standup meeting as having a timebox of 15 minutes where the team updates each other on work, which is good, but can be bad if driven or includes silent members or micromanaging. It also notes implementation talk and using the improvement board as ugly aspects.
Що ми будемо робити на вебінарі? Ми розберемо такі явища
✅ як нарцистичний розлад особистості,
✅ грандіозний нарцисизм,
✅ газлайтинг,
✅ знецінення,
✅ гойдалки вина-лють-вина,
✅ нарцистичне розширення,
✅ бомбардування любов’ю,
✅ мімікрування,
✅ створення ілюзорного майбутнього,
✅ контроль,
✅ спалахи гніву,
✅ вгадування майбутнього,
✅ вибір перебором, трошки хлібчика, щоб не подох,
✅ відштовхування/кидання/блокування,
✅ покарання мовчанням.
МАНІПУЛЯЦІЇ: ХТО КОГО І ДЛЯ ЧОГО? - Інна ТіторенкоDakiry
ВЕБІНАР: "МАНІПУЛЯЦІЇ: ХТО КОГО І ДЛЯ ЧОГО?":
Що таке маніпуляції?
Які бувають види маніпуляції, як їх відрізнити?
Хто і чому маніпулює?
Чи добре чи погано маніпулювати?
І звичайно, як їм протистояти?
Під час доповіді поговоримо про участь бізнес-аналітиків і розкриємо основні складові discovery workshop:
- Організація. Коли проведення воркшопу, окрім стартової фази, є максимально ефективним?
- Підготовка. Як почати з нічого і якісно підготуватись до воркшопу у стислі терміни?
- Проведення: Workshop Do’s and Don’ts. Приклади технік і вправ, а також приблизний план самого воркшопу.
- Оформлення кінцевих результатів або презентації, що запам’ятовуються
З понеділка йду на новий проект. The tester’s version - Олександра ЗубальDakiry
З понеділка йду на новий проект. The tester’s version - Олександра Зубаль:
- Коли тестувальнику починати тестувати? Очікування VS реальність
- Новий проєкт. Шо робити?
- Старий проєкт, але змінюється тестувальник. Шо робити?
- Як все зібрати докупи, розкласти по поличках і почати нормально спати ночами?
Oleh Shpyrna "Security Testing Basics: Check your Webapp for gaps before l_unch"Dakiry
This document provides an overview of security testing basics. It discusses adding security checks to testing by following best practices like the OWASP Top 10. The agenda includes who penetration testers are, integrating security into the SDLC, and basic tools for security testing like BurpSuite and Nmap. Common issues covered include injections, cross-site scripting, and insecure design. Resources are provided for training like PortSwigger Web Security Academy and HackTheBox.
Oleksandra Zubal "Project starters: test automation view"Dakiry
This document discusses test automation and the fundamental testing process. It covers the typical stages of testing including planning, monitoring and control, analysis and design, implementation and execution, and completion. Other sections provide overviews of typical industry domains for testing, considerations for planning like budget and dependencies, and important aspects of testing like goals, methodology, documentation and reporting, tools, and ensuring quality. The overall message is the importance of establishing a thorough and well-executed testing process to deliver high quality products and services.
Vladyslav Romanchenko "How to keep high code quality without e2e tests"Dakiry
This document discusses how to test React and Redux applications without end-to-end tests. It recommends using unit and integration tests instead to test individual components and functions. It provides examples of how to test helper functions, action creators, reducers, selectors, and component rendering and interactions using Jest and libraries like Enzyme. Key steps include mocking dependencies, dispatching actions, and asserting on output or UI states. Following these techniques allows testing isolated pieces and catching errors early without relying on unstable end-to-end tests.
Діана Пінчук "Як відрізнити авторизацію від аутентифікації та перестати бояти...Dakiry
Authentication (AuthN) is the process of verifying a person's identity, while authorization (AuthZ) determines what resources that person can access. AuthN uses factors like passwords, tokens, and biometrics to confirm someone is who they say they are. AuthZ implements access controls based on attributes, roles, rules or policies to govern resource permissions. Identity and access management (IAM) combines AuthN and AuthZ with user management to provide the right access to the right individuals. When testing, it is important to distinguish AuthN from AuthZ and understand how each can be exploited through vulnerabilities like weak credentials, authorization bypass, or privilege escalation.
Yuriy Malyi "E2E testing organization in multi-system projects"Dakiry
The document discusses end-to-end (E2E) testing organization for multi-system projects. It addresses determining team roles and responsibilities, defining the testing process and bug workflow, analyzing environments, and outlining steps for organizing E2E testing for project drops or releases. The presentation provides diagrams of user story and environment workflows and recommends getting an overall project picture, setting quality gates at each stage, and preparing test cases and environments to ensure smooth project drops or releases.
Petro Tarasenko "You've become a TL. What's next?"Dakiry
The document provides advice for a new QA team lead on next steps. It suggests creating a solid plan that addresses current challenges, future vision, timeline, and key performance indicators. The plan should be shared with key stakeholders like testing team, managers, developers, and product teams. It also emphasizes learning about priorities, challenges, and allies/detractors. Finally, it advises rehearsing the plan to concisely convey necessary information to busy managers.
Maryna Shulga "Mission Impossible. Впровадити тест процеси, якщо ніхто цього ...Dakiry
This document discusses an individual who is a test manager and provides various training services including QA fundamentals courses, ISTQB certification courses, and corporate soft skills training. It also mentions their work in industries such as healthcare, retail, and infrastructure. The document then discusses objections that can come up during presentations and how to address objections by turning them into benefits or requests for more information. It emphasizes that objections are not rejections but buying signals and opportunities to provide additional details.
QA manager Alona Tudan discusses her experience in QA and her dream of working with Microsoft Azure. She provides an overview of how to analyze logs and track failures on Azure using analytics queries. Tudan also demonstrates how to send and receive messages from Azure queues and topics using manual tools like Azure Storage Explorer and automated testing with Java code.
«Українська література» підручник для 5 класу закладів загальної середньої ос...ssuser5dd4af
Рекомендовано Міністерством освіти і науки України (Наказ Міністерства освіти і науки України від 08.02.2022 р. №140) Цей Підручник видано за підтримки Уряду Японії. Тлумачення та висновки в цьому Підручнику є позицією авторів і не обов’язково відображають політику чи погляди Уряду Японії.
«Українська мова» підручник для 6 класу закладів загальної середньої освіти (...ssuser5dd4af
Рекомендовано Міністерством освіти і науки України (Наказ Міністерства освіти і науки України від 08.03.2023 р. №254)
Видано державним коштом. Продаж заборонено
«Всесвітня історія» підручник для 7 класу закладів загальної середньої освіти...ssuser5dd4af
Рекомендовано Міністерством освіти і науки України (Наказ Міністерства освіти і науки України від 05.02.2024 р. №124)
Видано за рахунок державних коштів. Продаж заборонено
«Історія України. Всесвітня історія» підручник для 6 класу закладів загальної...ssuser5dd4af
Рекомендовано Міністерством освіти і науки України (Наказ Міністерства освіти і науки України від 08.03.2023 р. №254)
Видано за рахунок державних коштів. Продаж заборонено
«Біологія» підручник для 7 класу закладів загальної середньої освіти (авт. Ба...ssuser5dd4af
Рекомендовано Міністерством освіти і науки України (Наказ Міністерства освіти і науки України від 05.02.2024 р. №124)
Видано за рахунок державних коштів. Продаж заборонено
«Географія» підручник для 7 класу закладів загальної середньої освіти (авт. Б...ssuser5dd4af
Рекомендовано Міністерством освіти і науки України (Наказ Міністерства освіти і науки України від 05.02.2024 р. №124)
Видано за рахунок державних коштів. Продаж заборонено
«Українська література» підручник для 5 класу закладів загальної середньої ос...ssuser5dd4af
Рекомендовано Міністерством освіти і науки України (Наказ Міністерства освіти і науки України від 08.02.2022 р. №140) Цей Підручник видано за підтримки Уряду Японії. Тлумачення та висновки в цьому Підручнику є позицією авторів і не обов’язково відображають політику чи погляди Уряду Японії
«Українська література» підручник для 5 класу закладів загальної середньої ос...
Оля Фейдак “Is there life during regression?”
1. Is there life during
regression?
Tips & tricks how to survive
Olga Feidak
Software Testing Engineer
at EPAM Systems
2. Who am I ?
• Olga Feidak
• Software Testing Engineer
• 3 years in IT
• Desktop app, web admin part,
mobile iPad version
3. Agenda
•How people see the regression
•What is the regression?
•Pros and Cons of regression?
•How to tackle the Cons?
•Questions
4. Feedbacks
“Регресія - це перевірка існуючого
функціоналу після внесення змін або
рефакторингу. Зазвичай проводиться
вкінці спринта перед релізом”
“Безстрессове сіре існування.... ну і
після 18 години якісь пульси
життєві також дають знати”
“Регресія – це можливість вкотре
пройтися широкими шляхами та
вузькими стежками програми і
впритул поглянути на наслідки і
результати впроваджених змін”
“Регресія - це як щоденне піклування
про дитину :) - перевіряти, чи нема в
неї температури, чи вона не хвора, чи
поїла, добре вдягнена. Батьки, які
люблять дитину, не будуть від цього
рятуватись, бо це частина їх життя і
вони хочуть це робити”
5. What Regression testing is?
Regression testing - testing of a previously tested program following
modification to ensure that defects have not been introduced or
uncovered in unchanged areas of the software, as a result of the changes
made. It is performed when the software or its environment is changed.
(by ISTQB Glossary)
6. Pros of Regression Testing
❏ You check that APP is alive
❏ You give the client aproove that APP is alive
❏ You find new bug/improvements
❏ You check your test cases or develop new one
❏ You can use new approaches for testing
7. Cons of Regression Testing
❖ Repetitive activity
❖ No possibility to develop
❖ The Pesticide Paradox
❖ Boring routine
❖ Easy to procrastinate
❖ Takes time when no time is
❖ Rush within deadlines
8. 1. Workarounds (skip step, add step, repeat
step, replace steps)
How to tackle the Cons? Part 1
2. Is it mentioned in documentation?
3. Use end-to-end testing for each test case:
can you follow actions from the click
to the record in DB ?
4. How many? (ways, buttons, templates)
9. How to tackle the Cons? Part 2
5. Is the new forgotten old? - “Baby
approach”
6. Is the software defect-free? - No!
7. Three phase regression testing
10. Instead of summary
Regression becomes bad if only stop seeing it as the
possibility to find and learn something new in old.
Spice your tests a bit!
Editor's Notes
I’m working in the IT sphere approximately 3 years.
At EPAM Systems
Heas experience in desktop application testing
Main areas ofresponsibilities: Functional, Smoke, Regression testing
You may ask why i chose this topic? - the reason is we test application for each new build before it is presented and installed to the clients of our customer. Thus, regression is ‘daily bread’ of our testing activities
Starting to work on the topic I made little survey with question “ How do you see regression testing?” and ‘What is regression testing for you?’
The formal terms for the regression given by ISTQB
Повторювальні, механічні дії (пройти тест, поставити статус, написати відмітку, поставити поагний статус, описази дефект)
Поки ранаки тейси нові фічі, технології не використовуються
Парадокс пестициду - якщо мозок звик, що щось працює, не копає глибше і може новостворені дефекти знайти
Під час монотонної роботи легко відволіктися і не докопати якусь невідповідність зі степом чи отриманим результатом.
Регресія займає багато часу, (особливо під час повної регресії) фактично з нуля потрібно перевірити всі колись і тепер існуючі функціональності
Коли є дедлайни по регресії і великий скоуп починається паніка, що “Нічого не встигаєм” або “Всьо пропало!”.
Workround - can you avoid some steps? Can you repite some steps? Can you do same action in other way?
Read documentation again - You can find something new! And imagine new logical ideas can be found to be missed
End-To-End - follow the data pass or log tracking or data in DB update after each action or step
How many? - now many time can I repeate this step(clic kthe button, reload the page, generate the report, click edit, how many way to put file there)
What’s new - imagine you see your site, application for first time, as child do not know what the think is and try to make up what can do with it.
Use anger becease there is no defect-free softwave - you will fidn defect!
what can happen if ‘do not check if the child if worn or is walking with temperature?’
Three phase-1. Focused regression(the las fixes or new functionality connected with old one) Expanded regression (usually automated , for functionality not directly connecte to the changes functionality) New relese functionality regression - wefocus only on the newlyadded functionality and select only 30 % of the created cases - all of it helps to reduce the period andeffor of regression testing
Just remember every new view can find some inconsistency or defect or bug. But it depends on the person - it will be your view or somebody’s else.
Defect-free software does not exist. - The regression is time span to make APP better.