Browser automation testing tips - Githubissues

testdouble / jasmine-example

testdouble.com

1 stars 5 forks source link

Browser automation testing tips #13

Open searls opened 9 years ago

searls commented 9 years ago

There are a handful of pieces of general advice for writing solid browser automation tests we can review:

Selecting on user-visible text, and falling back on semantically meaningful attributes like rel as opposed to IDs & classes that are potentially significant to the implementation
Automating a11y testing
Superlinear build growth due to naive CRUD feature testing
After-action reports to actively identify and work to prevent against false negative test failures
Time-boxing the overall build to guard against bloat and ensure fast feedback

sarkasm commented 9 years ago

:+1:

incredisys commented 9 years ago

+1

ericgrigorian commented 9 years ago

:+1:

Avienneau commented 9 years ago

:+1:

ghost commented 9 years ago

+1

ianjmacintosh commented 9 years ago

:+1:

cselemon commented 9 years ago

Def

chetushivanna commented 9 years ago

+1

sheeralal commented 9 years ago

+1

vjmurphy commented 9 years ago

:+1:

ubalusamy commented 9 years ago

:+1:

chetushivanna commented 9 years ago

+1

akotagiri commented 9 years ago

+1

mcushman commented 9 years ago

+1

TevK commented 9 years ago

:+1:

ravirkulkarni commented 9 years ago

:+1:

vinayanuthakki commented 9 years ago

:+1:

treshma commented 9 years ago

+1

hparekh1 commented 9 years ago

:+1: