making your results visible - a test result dashboard and comparison tool
TRANSCRIPT
REPAUTOReporting made better
INTRODUCTIONJames 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…
THANKS TO
• Sumit Poddar• Tim Goodwin• Brian Brewer
• Team at FISERV (Especially Tristan Worley)
STORY TIME
Sometimesthings just go
WRONG
AUTOMATION EVERYWHERE what, where, who?
“So, for our XXXXX iPhone app we have 8 UNIT TESTS all together. One of the unit tests is just an EXAMPLE though. ☺ ”
-Developer(Yes he really did put the smiley face in there)
WHY are we doing this?
One framework to rule them all…and selenium to bind them
Seconf 14 - Allure
http://allure.qatools.ru
Thousands ofTESTS
9/10 testers agree ‘FLAKES are bad’
Devices are HARD
ANYTHING can go wrong
ANYTHING…
So many DEVICES
Network PROBLEMS…
Boy who CRIED wolf
Information OVERLOAD
DEBUGGINGis hard
Why don’twe try
something NEW?
CENTRALIZED
Pick out the FLAKES
HISTORY and COMPARISON
Easy TRIAGING
How di
d we BUILD it?
Allure ADAPTORS
MV
C
Thin Model
Controller Simplified
https://github.com/xiaoxinghu/datacraft
$ dcraft build sync.rb
Same Good View
Positive feedback => [email protected] Technical support => [email protected] Negative feedback => [email protected] Github – https://github.com/xiaoxinghu/repauto
FEEDBACK / QUESTIONS