Sikuli for Mobile Testing

5,006 views
4,676 views

Published on

By Tom Yeh, University of Boulder

0 Comments
7 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
5,006
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
100
Comments
0
Likes
7
Embeds 0
No embeds

No notes for slide
  • GUI testing is hard to automate because it is about user experienceAbout interacivtyAbout what users doAbout what they see
  • GUI testing is hard to automate because it is about user experienceAbout interacivtyAbout what users doAbout what they see
  • Sikuli for Mobile Testing

    1. 1. SIKULI for Mobile Testing Tom Yeh Assistant Professor Department of Computer Science University of Colorado Boulder Mobile Testing Summit 2012
    2. 2. Visual Diff
    3. 3. Test 1 Test 2 Test 3 Test 4 Test 5build012
    4. 4. Test 1 Test 2 Test 3 Test 4 Test 5build012build013
    5. 5. Test 1 Test 2 Test 3 Test 4 Test 5build012build013 Are they different?
    6. 6. Test 1 Test 2 Test 3 Test 4 Test 5build012build013
    7. 7. Step 1: Click on
    8. 8. Think programmingWhich row?Which column?What component ID?What name?What label?
    9. 9. Think SikuliWhich does it look like?
    10. 10. Step 1: Click on
    11. 11. Step 1: Click on
    12. 12. Goal:Uncheck Contacts
    13. 13. What’s wrong?
    14. 14. Harvard Medical School
    15. 15. Too Visual
    16. 16. 400manual test cases 5 hours of labour
    17. 17. 2xrelease rate
    18. 18. TELENAVGPS App Maker
    19. 19. Too New
    20. 20. Tests areautomated via emulators
    21. 21. NASA
    22. 22. Too Old
    23. 23. NASA’s part supplier
    24. 24. Tests are automated through a remote desktop connection
    25. 25. Too Visual Too New Too Old
    26. 26. What’s coming?
    27. 27. http://www.cuberick.com/2010/06/testing-image-generation-with-cucumber.html
    28. 28. Mobile Testing goes Physical
    29. 29. Mobile Testing goes Physical Visual
    30. 30. Baxter by Rethink Robotics
    31. 31. Baxter by Rethink Robotics

    ×