Привет всем! Сегодня мы поговорим о тестировании. Предположительно темы будут следующие: 1. Дискуссия: "Различные инструменты управления тестами в Atlassian Jira" 2. Test Management for Jira, представители Adaptavist расскажут об их инструменте 3. Процесс тестирования в Itiviti FYI: Регистрация обязательна на сайте мероприятия: https://aug.atlassian.com/events/details/atlassian-st-petersburg-presents-nemnogo-o-testirovanii-instrumenty-protsessy#/ В 12:00 будут заказываться пропуска и логины и пароли для гостевого Wifi.

2. Vitor Pelizza
Tech Lead @ Test Management for Jira
vpelizza@adaptavist.com

3. About Adaptavist
• Atlassian Solution Partner for Enterprise
• Platinum Solution Partners having met Atlassian’s highest training criteria and have a proven practice that
can scale to the largest Enterprise customers.
• Exclusively focused on Atlassian solutions
• Resourced to manage a wide range of support requirements, implementations, and customer specific
solutions.
• Go to Experts within Atlassian Ecosystem
• Adaptavist have been working with the Atlassian toolset since 2005 and seen as a ‘go-to’ expert for
strategy, implementation and support services with 23 apps on the Atlassian marketplace

4. Why Test?

6. Why
Test?

7. Why Test?

8. Can we manage tests in Jira?

10. Track testing progress and
software quality
Foster collaboration and visibility of both
traditional and agile teams
Integrate with test
automation
With our powerful REST API
Full-featured test
management solution
Seamlessly integrated into Jira's user interface.
No need to learn - or switch between - different
environments
Test
Management
for Jira

11. Versioning
Versioning for
test cases
Version allows teams to
collaborate and manage
multiple versions of test
cases in parallel while
keeping data integrity and
providing an audit history of
changes. Versions can be
viewed and compared for
audit purposes

12. Shared steps
Share steps
between test cases
to eliminate
duplication
When creating new tests or
editing existing tests, it is
possible to reuse test steps from
other existing tests from any Jira
project. This feature can save
time and eliminate duplication

13. Impact analysis
Enhanced
traceability for
coverage and
impact analysis
Powerful traceability
capabilities and reports which
lets you focus on test coverage
and root cause analysis
Know ahead of time how a
change is going to impact
requirements and test cases

14. DEMO

15. • Atlassian Verified
• Top reviewed add-on for Testing & QA
• Perfect for agile & traditional testing approaches
• Better usability & familiar user interface
• Fast & friendly support
• User centric roadmap
• Monthly releases
Why businesses of all sizes choose Test Management for Jira

16. Enterprise Ready and Ready to Go
Cloud Server Datacenter
Cloud Server Datacenter
Enterprise Ready and Ready to Go

17. Adaptavist Toolchain Integration with the Atlassian Ecosystem

18. Vitor Pelizza
vpelizza@adaptavist.com
Questions?
Find out more and start a trial at
adaptavist.com/atlassian-apps/test-management-for-jira/

19. Thank you

20. Храним тесты в JIRA:
обзор плагинов

21. Кто я?
• Юля
• QA Lead @ ALM Works
• Люблю кофе
• Предпочитаю среды
понедельникам

22. О чем доклад?
• У нас уже есть JIRA. Куда
писать тесты?
• Как много всего. Что же
выбрать?

23. У меня есть JIRA
и есть тесты. Как
бы их
соединить?
сделать все
ручками. нужна
только JIRA
Хранить тесты в
стороннем
приложении с
коннектором для
JIRA
Хранить тесты
прямо в JIRA с
использованием
плагинов

24. JIRA: Настраиваем сами
• Cоздаем отдельный тип
задачи (Test)
• Создаем свой workflow
• Настраиваем custom
fields
• Долгo, муторно, сложно с
переиспользованием
• Дешево (если не
учитывать время :)

25. JIRA: Готовый Workflow
Test Case Workflow

26. Стороннее приложение с коннетором
• Большой выбор
• Тесты живут в
стороннем приложении
• Ничего не нужно
переносить при смене
трекера
Hiptest
qTest
PractiTest
Enterprise Tester
Test Lodge
Zephyr Enterprise
QMetry

27. Moqa
• Быстро проставлять
результаты тесто
• Всмотреть количество тестов
по статусам
• Доступен для iOS, Android
• Интеграция с Test Rail,
Structure.Testy

28. Готовые плагины для JIRA
• Все в одном месте, не
нужно менять контекст,
прозрачность работы
• Как правило недешево
(стоимость по JIRA
лицензии)
• В Cloud версии выбор
небольшой
Intriguing

29. Zephyr for JIRA + ZAPI

31. Xray

33. Adaptavist Test Management
(Kanoah Tests)

35. QA Space

37. Structure.Testy

39. Рассказывайте нам о
ваших предложениях
и наших багах
Подписывайтесь на наш
канал
Пишите письма:
ja@almworks.com
https://www.youtube.com/ALMWorksChannel

40. Testing
process & tools
Anzhelika Deryabina, Associate QA Engineer
St Petersburg, March 2018

41. © Itiviti AB. All Rights Reserved. Proprietary and Confidential.
Agenda
Itiviti: testing process, principles
Continuous Delivery Pipeline
Test Quadrant
Atlassian tools for Continuous Delivery
Bug reporting
JIRA Issue Workflow
General
Test Case Template
Test Case
Test Plan

42. © Itiviti AB. All Rights Reserved. Proprietary and Confidential.
Continuous Delivery

43. © Itiviti AB. All Rights Reserved. Proprietary and Confidential.
Continuous Delivery Pipeline

44. © Itiviti AB. All Rights Reserved. Proprietary and Confidential.
Test Quadrant

45. © Itiviti AB. All Rights Reserved. Proprietary and Confidential.
Atlassian

46. Bug Reporting

47. © Itiviti AB. All Rights Reserved. Proprietary and Confidential.
How to report a bug?
Search for a duplicate
key
component
version
text ~ "crash" and component = “component_name" and project = “project_name" and
affectedVersion in (“v1", “v2.3")
Collect logs
Project, component
Provide a descriptive summary of the issue to conceptually understand the problem
Attach screenshots
Steps to reproduce
Expected result and actual result
Links to related cases

48. © Itiviti AB. All Rights Reserved. Proprietary and Confidential.
Bug report Example

49. JIRA Issue Workflow

50. © Itiviti AB. All Rights Reserved. Proprietary and Confidential.
JIRA Issue Workflow
Workflow Issue Types
Default workflow • Bug
• Improvement
• New Feature
• Performance improvement
• Performance regression
• Task
• Sub-Task
Test Case • Test Case
Test Plan • Test Plan

51. © Itiviti AB. All Rights Reserved. Proprietary and Confidential.
General Workflow

52. © Itiviti AB. All Rights Reserved. Proprietary and Confidential.
General Concept

53. © Itiviti AB. All Rights Reserved. Proprietary and Confidential.
Test Case Template Workflow
1. Create/update Test Cases
2. Define list of steps, group steps
3. Categorize test using test type, version
4. Connect tests with requirements
5. Test Progress of all executable copies

54. © Itiviti AB. All Rights Reserved. Proprietary and Confidential.
Test Case Template Example

55. © Itiviti AB. All Rights Reserved. Proprietary and Confidential.
Test Case Workflow
"In Progress" -> "Passed":
1. All steps should have status. (find the empty statuses)
2. Any steps has not to be on "In Progress"
3. Any steps has not to be on "Failed"
"In Progress" -> "Failed":
1. All steps should have status. (find the empty statuses)
2. Any steps has not to be on "In Progress"
3. One or more steps should to be in "Failed" status.

56. © Itiviti AB. All Rights Reserved. Proprietary and Confidential.
Test Case Example

57. © Itiviti AB. All Rights Reserved. Proprietary and Confidential.
Test Plan Workflow
1. Create, copy Test Plan
2. Create, update, assign Test Cases
3. Connect Test Plan with requirements/defects
4. Track progress
5. Aggregate Defects
6. Estimate and log work using JIRA Time Tracking
7. Group Test Cases under Test Plan

58. © Itiviti AB. All Rights Reserved. Proprietary and Confidential.
Test Plan Example

59. itiviti.com