Reducing False Positives In Automated Testing

transcript

Reducing False Positives

inAutomated

Testing

FALSE POSITIVES ARE “FAILED”TESTS THAT SHOULD HAVE PASSED,

aka FALSE ALARMS.

WHY DO THEY OCCUR?

• AUTOMATION APPROACH

WHY DO THEY OCCUR?

• AUTOMATION APPROACH• IMPLEMENTED FRAMEWORK

WHY DO THEY OCCUR?

• AUTOMATION APPROACH• IMPLEMENTED FRAMEWORK• THE WRITTEN TEST ITSELF

THERE ARE SEVERAL POTENTIALCAUSES FOR FALSE POSITIVES IN

AUTOMATED TESTING:

RELYING ON UI

Cause #1:

Small changes in UI can causetest breakage

CHANGE INUI ELEMENTPROPERTIES

Cause #2:

Any change to:

CLASS NAME

Can result intest breakage

SHAREDENVIRONMENTS

Cause #3:

Functional & automated testing

require separate environments

REFERENCEDATA CHANGE

Cause #4:

Scripts may changeconfiguration data

required by a test

SLOWPERFORMANCE

Cause #5:

Slow performance =Slow test execution

& test failure

MANUALINTERVENTION

Cause #6:

Some data must be cleared manually

before/aftertest execution

RELYING ONSEQUENCE OF

EXECUTION

Cause #7:

Any failure intest sequenceimpacts the entire

test suite

KEYS TOREDUCING

FALSE POSITIVES

USE OPTIMAL CONFIGURATIONS

CONTROLLED AUTOMATION ENVIRONMENT

KEEP TESTS SHORT

KEEP TESTS INDEPENDENT

KEEP TESTS SHORT

KEEP TESTS INDEPENDENT

USE RIGHT LOCATORSFOR OBJECT IDENTIFICATION

VIEW THE ENTIRE

QASOURCEWEBINAR

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

Reducing False Positives In Automated Testing

Software