Chat based Testing is basically extending ChatOps to testing that will keeps the people involved in software development more connected and facilitates conversation-driven development.

1. TESTING AS A
CHAT
TESTING ANYTHING FROM
ANYWHERE AS A CHAT
CONVERSATION
IRFAN AHMAD
Web irfanahmad.in
Twitter @notimewaste

2. WHY THIS TALK ….
who will run business when you are
busy saving the world?

3. OUTLINE
▸Why?
▸What?
▸How?
▸Really?
▸What Next?

4. WHY ?

5. TEAM COMMUNICATION

6. 1.Emails
2.Chats
3.Meetings
4.Physical
41%
14%
9%
36%
CONVERSATIONS HAPPENING?

7. WHAT DO WE COMMUNICATE ?
1.Data
2.Requests
3.Tests
4.Code
5.Results
6.Problems
7.Solutions

8. 1.Quicker Release Cycles
2.CAMS (Culture of
Automation ,Measurement and Sharing )
3.Visibility across the teams
READY TO CATCH UP?

9. WHAT ?
CHATOPS

10. bringing in the work you are
already doing in line with the
conversations you are already
having
WHAT IS CHATOPS?
putting tools in the middle
of the conversation

11. COMMON USE CASES?
1.pushing context
2.pulling information
3.bidirectional interactions
4.custom tasks
5.third party integrations

12. HOLDS VALID FOR TESTING?
1.pushing context - test results
2.pulling information - query status
3.bidirectional interactions - running tests
4.custom tasks - CI/CD/Releases
ChatOps is limited to mostly Ops :(

13. CHATOPS +
TESTING =
AWESOENESS

14. STORY TIME - HOW QA RELEASES HAPPEN

15. ROLE - CHATBOT
GOAL : TAKE OUT A NEW
‘SIMRAN’ TO LIVE
RAJ [RELEASE
AUTOMATION JANITOR]

16. ROLE - RELEASE BUILD
GOAL : GO LIVE ASAP
SIMRAN [SOFTWARE
IMPLEMENTATION OF
REQUIREMENTS
AUTHORED BY NERDS]

17. ROLE - QA
GOAL : TAKE CARE OF
‘SIMRAN’
BABUJI [BODYGUARD
OF AGENCY, BUGS IN
USER JOURNEY AND
INCIDENTS]

18. ROLE - DEVELOPER
GOAL : SEE ‘SIMRAN’
LIVING HER LIFE
MAA [MOTHER OF ALL
APPS]

19. ROLE - PRODUCT OWNER
GOAL : SEE ‘SIMRAN’
CHILDREN AND HER
FAMILY GROWING
MAAA [ MOTHER OF ALL
ARBITRARY
ASSUMPTIONS

20. HOW ?

21. 1.chat platform
2.bot framework
3.service integration
4.culture
PRE-REQUISITES

22. 1.Hubot
2.Lita
3.Errbot
4.Cog
5.Yetibot
BOT FRAMEWORK

23. USING ONLY NATIVE THIRD PARTY INTEGRATIONS

24. EVALUATING BOT FRAMEWORKS

25. ARCHITECTURE - WITH TESTS AS API’S
https://www.draw.io/#G0B7yugxIPUTaVUWhjbHVoRFNRY2s

26. Deliver API and Web Test via Chat to Test a Voting App
1.By running over CI Tools
2.By Exposing tests as service
3.Show Testing Results
4.Anyone should know status with Query
EG. PROBLEM

27. EXAMPLE VOTING APP : COMPONENTS

28. VOTING APP : APP UNDER TEST
▸ Simple Real Time voting app
▸ Testing Scenarios implemented for api
and web

29. REALLY?
A ) DEMO1 - USING CI
https://youtu.be/zfBGsDql5d4

31. DEMO 2 - USING
TESTS API
https://www.youtube.com/watch?
v=bLOP3v_CkBA

33. SOLVE ALL PROBLEMS ?
Problems Solved
Visibility Yes
Culture possible
Automation Yes
Mesurement possible
Sharing Yes

34. BEST PRACTICES
▸ Cultural acceptance first ,technology
second
▸ Signal to Noise
▸ Security
▸ Open source vs SaaS Alternatives

35. WHAT NEXT ?

36. CHALLENGES
▸ Adoption
▸ Tools support
▸ Signal to noise
▸ Security
▸ Exposing tests as service

37. Q
&
A
THANK
YOU
Open Sourced - For Hands On
Github
https://github.com/notimewaste/TestStack
https://github.com/notimewaste/chatter
https://github.com/notimewaste/example-voting-app
API
https://app.apiary.io/teststack/
IRFAN AHMAD
Email irfan@critick.io
Web irfanahmad.in
Twitter @notimewaste