This document introduces REPAUTO, a test automation framework that aims to address common issues like flaky tests. It summarizes the key problems such as the large number of tests, devices and networks that can cause failures, and the difficulty of debugging issues. The framework proposes centralized logging, history comparison and flake detection to make triaging easier. It was built with technologies like Allure and MVC, and the source code is available on GitHub for feedback.

1. REPAUTO
Reporting made better

2. INTRODUCTION
James Farrier
• Test Engineering Lead Fiserv
• Love warm weather and walks along the beach
Xiaoxing Hu
• Test Engineer
• Evangelizing Ruby to C# developers
• Don’t try to poach him! I will be watching…

3. THANKS TO
• Sumit Poddar
• Tim Goodwin
• Brian Brewer
• Team at FISERV
(Especially Tristan Worley)

4. STORY TIME

5. Sometimes
things just go
WRONG

6. AUTOMATION EVERYWHERE
what, where, who?

7. “So, for our XXXXX iPhone app we have
8 UNIT TESTSall together.
One of the unit tests is just an
EXAMPLEthough. ☺ ”
-Developer
(Yes he really did put the smiley face in there)

8. WHY are we doing this?

9. One framework to rule them all…
and selenium to bind them

11. Seconf 14 - Allure
http://allure.qatools.ru

13. Thousands of
TESTS

14. 9/10 testers agree ‘FLAKES are bad’

15. Devices are HARD

16. ANYTHING
can go wrong

17. ANYTHING…

18. So many DEVICES

19. Network
PROBLEMS…

20. Boy who CRIEDwolf

21. Information
OVERLOAD

22. DEBUGGING
is hard

24. Why don’t
we try
something
NEW?

25. CENTRALIZED

27. Pick out the
FLAKES

28. HISTORY and COMPARISON

29. Easy TRIAGING

32. How
did
we
BUILD it?

33. Allure
ADAPTORS

34. M
V
C

35. Thin Model

37. Controller Simplified

39. https://github.com/xiaoxinghu/datacraft

40. $ dcraft build sync.rb

41. Same Good View

42.
Positive feedback => jamesfarrier@gmail.com
Technical support => dawnstar.hu@gmail.com
Negative feedback => jamesfarrier+spam@gmail.com
Github – https://github.com/xiaoxinghu/repauto
FEEDBACK / QUESTIONS