1 / 31

Reducing False Positives In Automated Testing

In conjunction with Sauce Labs, QASource presented a webinar, "Reducing False Positives With Automated In Automated Testing". This slide deck summarizes the key points of the presentation. To view the complete webinar, visit: https://youtu.be/bi8hDBoZMPY Subscribe to the QASource YouTube channel for future webinars and other engaging video content!

QASource
Download Presentation

Reducing False Positives In Automated Testing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Reducing False Positives in Automated Testing

  2. FALSE POSITIVES ARE “FAILED” TESTS THAT SHOULD HAVE PASSED, aka FALSE ALARMS.

  3. WHY DO THEY OCCUR?

  4. WHY DO THEY OCCUR? • AUTOMATION APPROACH

  5. WHY DO THEY OCCUR? • AUTOMATION APPROACH • IMPLEMENTED FRAMEWORK

  6. WHY DO THEY OCCUR? • AUTOMATION APPROACH • IMPLEMENTED FRAMEWORK • THE WRITTEN TEST ITSELF

  7. THERE ARE SEVERAL POTENTIAL CAUSES FOR FALSE POSITIVES IN AUTOMATED TESTING:

  8. Cause #1: RELYING ON UI

  9. Small changes in UI can cause test breakage

  10. Cause #2: CHANGE IN UI ELEMENT PROPERTIES

  11. Any change to: ID

  12. Any change to: ID CSS

  13. Any change to: ID CSS CLASS NAME

  14. Can result in test breakage

  15. Cause #3: SHARED ENVIRONMENTS

  16. Functional & automated testing require separate environments

  17. Cause #4: REFERENCE DATA CHANGE

  18. Scripts may change configuration data required by a test

  19. Cause #5: SLOW PERFORMANCE

  20. Slow performance = Slow test execution & test failure

  21. Cause #6: MANUAL INTERVENTION

  22. Some data must be cleared manually before/after test execution

  23. Cause #7: RELYING ON SEQUENCE OF EXECUTION

  24. Any failure in test sequence impacts the entire test suite

  25. KEYS TO REDUCING FALSE POSITIVES

  26. USE OPTIMAL CONFIGURATIONS

  27. USE OPTIMAL CONFIGURATIONS CONTROLLED AUTOMATION ENVIRONMENT

  28. USE OPTIMAL CONFIGURATIONS CONTROLLED AUTOMATION ENVIRONMENT KEEP TESTS SHORT

  29. USE OPTIMAL CONFIGURATIONS CONTROLLED AUTOMATION ENVIRONMENT KEEP TESTS SHORT KEEP TESTS INDEPENDENT

  30. USE OPTIMAL CONFIGURATIONS CONTROLLED AUTOMATION ENVIRONMENT KEEP TESTS SHORT KEEP TESTS INDEPENDENT USE RIGHT LOCATORS FOR OBJECT IDENTIFICATION

  31. VIEW THE ENTIRE QASOURCE WEBINAR AND READ THE COMPLETE Q & A: Pre and Post Webinar Questions Answered: Reducing False Positives in Automated Testing QUESTIONS ABOUT FINANCIAL TESTING? VISIT US AT QASOURCE.COM

More Related