Top Banner
WHY TEST?
25

Testing intro

Jan 18, 2017

Download

Software

Ivan Storck
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Testing intro

WHY TEST?

Page 2: Testing intro

Performance Testing

$ siege -n1000 -c10

or LoadImpact.com

Page 3: Testing intro

Functional Testing / Form Validation

Page 4: Testing intro

#a11y = accessibility

Page 5: Testing intro
Page 6: Testing intro

YOU HAVE A TEST PLANYou point, and click, and click, and point, and type…

You just haven’t written it

Write it down

Better yet, automate it!

Page 7: Testing intro
Page 8: Testing intro

NO EXCUSESI don't know

It's too hard

I don't have time to do any extra work

It's not my job

Page 9: Testing intro

Consider that your job is tobuild stuff that works.

You have an obligation to see if it works, right?

Page 10: Testing intro

over 25 years ago

Page 11: Testing intro

You can't optimize what you don't measure

Page 12: Testing intro

Google recommends your page should load in < half a second.

Page 13: Testing intro

#A11Y

http://squizlabs.github.io/HTML_CodeSniffer/

Page 15: Testing intro

REGRESSION TESTINGWhen you your customers find a bug,

how do you make sure it doesn't happen again?

Page 16: Testing intro

CUCUMBERRuby, JavaScript, Java or C#

Page 17: Testing intro

TESTS = SPECIFICATIONS = DOCUMENTATION

Page 18: Testing intro

TESTS = REDUCE THE FEAR OF CHANGE

Page 19: Testing intro

MORE TOOLS

Page 21: Testing intro

Automated, Cross-Browser Testing

Page 23: Testing intro

A11Y ON NPMa11y npm module

Page 24: Testing intro

DON'T FORGETMONITORING!

New Relic

Page 25: Testing intro

IVAN STORCKWeb developer, Teacher, Entrepreneur

UW PCE Advisory Board member: Ruby, JS, HTML5

Developer EvangelistAerobatic

@ivanoats

IvanStorck.com

linkedon.com/in/ivanoats