Техники тест-дизайна – «математика» тестирования. Новые техники появляются достаточно редко. 2 года назад вышла книга Сэма Канера «The Domain Testing Workbook”. Давайте посмотрим на технику доменного тестирования, и попробуем разобраться, новая ли это техника, или переформулированная старая? Что общее и что отличает доменное тестирование от других техник тест-дизайна? Мы также рассмотрим на практике несколько примеров применения доменного тестирования, а также ее применимость и перспективы.
5. 1. A Test Strategy document is a high level document and normally
developed by project manager
2. The Test Strategy document is a static document meaning that it is
not updated too often
3. Test strategy is a set of guidelines that explains test design and
determines how testing needs to be done
4. Some companies include the “Test Approach” or “Strategy” inside
the Test Plan, it is usually the case for small projects. For larger
projects, there is one Test Strategy document and different number
of Test Plans for each phase or level of testing.
Какие определения верны, какие – нет?
6. 1. A Test Strategy document is a high level document and normally
developed by project manager
2. The Test Strategy document is a static document meaning that it is
not updated too often
3. Test strategy is a set of guidelines that explains test design and
determines how testing needs to be done
4. Some companies include the “Test Approach” or “Strategy” inside
the Test Plan, it is usually the case for small projects. For larger
projects, there is one Test Strategy document and different number
of Test Plans for each phase or level of testing.
Ответы:
10. 1. Начинаем с продуктовых рисков
• Product risk is the possibility that the system or
software might fail to satisfy or fulfill some reasonable
expectation of the customer, user, or stakeholder.
(Some authors also called the 'Product risks' as
'Quality risks' as they are risks to the quality of the
product.)
ISTQB Glossary
11. Специфичные продуктовые риски
• Complex features affecting multiple areas of the existing product, like
an upgrade/migration of the system.
• New Technologies used in the product; for example a new DB server,
a new programming language, a new integration, etc.
• New Developers or Development Teams, who may lack experience
and thus pose a higher risk to the existing product.
• Tight Schedules, that make people work in a rush and commit more
mistakes
Joel Montvelisky “The simple differences between Product Risks &
Project Risks”
19. 2. Model-based подход
+ Структурированный подход
+ Лучшие практики (Best Practices)
+ Покрытие
+ Сравнимость
- Нет контекста проекта
- Слепота модели
- Недостаточно навыков
21. 3. Аналитический подход, шаги
• Выбор областей для причинно-следственного
анализа
• Сбор и организация информации
• Определение корневой причины (root cause)
• Выбор решения проблемы
22. 3. Пример аналитический подхода –
категоризация дефектов
Instead of studying and learning from every bug, you can save a lot of
time by counting and aggregating bug reports.
That’s a good thing in its way, because if you don’t study and learn from
every bug, you’ll need all the time you can get to deal with problems that
seem to keep happening over and over again.
Michael Bolton, “Very short blog post” №27
25. 1. Доклады о тестовых стратегиях
• Сергей Мартыненко ” Подготовка стратегии тестирования под
высокорискованный, высокодоходный проект” -
https://www.youtube.com/watch?v=z3NuJb0_MzI
• Testing Strategies for Continuous Delivery -
https://www.youtube.com/watch?v=DgQWSaCQ82U
• Huib Schoots “Practical Test Strategy Using Heuristics” -
https://www.youtube.com/watch?v=_TE9RFzNs_M
• Rikard Edgren “An Introduction to Test Strategy” -
https://www.youtube.com/watch?v=OZiE9eApOXY
• Paul Gerrard “Agile Test Strategy” -
https://www.youtube.com/watch?v=Ed6YkYEkCRM
• Radio QA “Выпуск 10: стратегия тестирования» - http://radio-
qa.com/vypusk-10-strategiya-testirovaniya/
26. 2. Книги о стратегиях
• Ричард Румельт «Хорошая стратегия, плохая
стратегия»
• Джим Коллинз «От хорошего к великому»
• Coursera “Foundations of Business Strategy” + book
• …
One or more of the following approaches can assist in selecting the right items for causal analysis:
The Pareto Principle (80/20 rule)
Defect categorizations
Analysis of statistics
Holding project retrospective meetings
