Download as PDF, PPTX
Uploaded bySAP SE
Testing without assertions - #HUSTEF2019
The document introduces a novel approach to test automation that emphasizes validating outcomes rather than defining them, focusing on version control rather than traditional testing methods. It discusses the challenges of noise and redundancy in automated tests and the importance of maintainable testing through features like ignore-lists and unbreakable selenium. Additionally, it highlights user feedback on the effectiveness of the tool and invites users to support it on GitHub.
More Related Content
Testing without assertions - #HUSTEF2019
- 1. @roesslerj1 Dr. Jeremias Rößler(Roessler) https://retest.de Test Automation without Assertions
- 2. @roesslerj2 Please star uson GitHub! Everyone who gives us a GitHub star, gets a sticker.
- 3. @roesslerj3 expect(umbrellaOpens).toBe(true) tests: 1 passed,1 total **all tests passed**
- 4.
- 5. @roesslerj5 We do onething different.
- 6. @roesslerj6 You don’t definethe outcome, you approve it. First you ensure that everything is as wanted. Then we make sure it doesn’t change.
- 7.
- 8.
- 9. @roesslerj9 Where has the Codechanged?
- 10.
- 11.
- 12.
- 13.
- 14.
- 15. @roesslerj15 Two Challenges: 1) Noise 2)Redundancy
- 16.
- 17.
- 18.
- 19.
- 20.
- 21.
- 22.
- 23. @roesslerj23 # These filesare ignored by git # based on their name: *.log *.class target/.* .gitignore
- 24. @roesslerj24 # Ignore filefor recheck. # Ignore attributes globally: attribute=class .retest/recheck.ignore
- 25. @roesslerj25 # Ignore filefor recheck. # Ignore elements by attribute: matcher: id=banner .retest/recheck.ignore
- 26. @roesslerj26 # Ignore filefor recheck. # These can be combined: matcher: id=div-b4f23, attribute-regex: font.* .retest/recheck.ignore
- 27.
- 28.
- 29.
- 30.
- 31.
- 32.
- 33.
- 34.
- 35.
- 36. @roesslerj36 new version findElement(by.id(“sign-in”)) ID changed use newelement and log find in old version old version breaks create 1-on-1 assignment new version best match
- 37. @roesslerj37 *************** recheck warning*************** The HTML id attribute used for element identification changed from 'username' to 'asda'. retest identified the element based on the persisted Golden Master. If you apply these changes to the Golden Master , your test de.retest.recheck.example.MyUnbreakableSeleniumTest will break. Use `By.id("asda")` or `By.retestId("username-1")` to update your test MyUnbreakableSeleniumTest.java:27.
- 38.
- 39. @roesslerj39 findByRetestId best match return Element findin Golden Master 1-on-1 Assignment Test
- 40.
- 41.
- 42.
- 43. @roesslerj43 + rule-based deterministicignore + open source + offline usage + unbreakable selenium + works for any technical interface recheck benefits:
- 44. @roesslerj44 some Feedback … Iwas thrilled by that product and new approach… … let me congratulate you on your brilliant idea of the unbreakable Selenium and the web page difference checking solutions. I think this is a very much needed solution in the website testing field. Ahmed Magdy Michael Wowro … the tool is very helpful, gives detailed information and is easy to use … Karolina Wierbol
- 45.
- 46.
- 47.
- 48.
- 49. @roesslerj new version findElement(by.id(“sign-in”)) ID changed use newelement and log find in old version old version breaks create 1-on-1 assignment new version best match @roesslerjX Better than pixel diffing 49 Difference Testing whitelist testing easy creation easy maintenance Unbreakable Selenium: easy to use define own ids data-independent tests Summary
- 50.