Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Spectrum Testing - Unit to Browser before Deploy

Web Applications have many places which can be tested in isolation and covered as a whole. If you’re not testing, you’re coding and praying.
by

Alan Blount

on 14 September 2015

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Spectrum Testing - Unit to Browser before Deploy

Coily's Development Style:
I built it.
It works.
I deployed it.
It works...
I'm good now, right?
Coily
Slick
Q-Bert
"Type and Pray"
Q-Bert's Development Style:
"Outside In, BDD & TDD"
Unit Test
Integration Test
UI Test
Manual Test
Acceptance Test
Spectrum Testing
Unit
to
Browser

Alan Blount
before Deploy
before any Pull Request / Merge
on every Commit
Alan Blount
@zeroasterisk
Web Developer
PHP, JS/NodeJS, Go
Why Testing?
Which Testing?
TDD / BDD
Layers of Tests
Slimming the Stack
(a bit)
NightwatchJS
(Cubumer)
TravisCI
(Jenkins)
MeteorJS
(AngularJS)
Contributor @ JSLou
& Kentucky Open Source Society
Topics / Technologies
No Testing = Bad Developer
?
Unit Test
E2E Test
Spectrum Test
Manual Test
UI
Acceptance
Integration
Slick's Development Style:
Write unit tests
Wire together parts
Test integrated whole
Test User Intent
Test User Interface
"Test Everything!"
WebKit & Headless
Gecko & Not (yet) Headless
scriptable browsers for Web developers
Continuous Integration
deprecates:
Angular Scenario Runner
Unit Testing &
(mocked)
Integration
run "on save"
(watcher)
E2E Testing
(Real World)
run "on commit"
(manual or CI)
Write Tests
Drive Browser
v 1.0.0 / 2011-10-06
v 1.0.0 / 2010-09-14
v 1.0.0 / 2012-03-24
"Test Runner"
and more....
"Testing Toolsets" & "Assertion Libraries"
... Or Write Stories, and Tests
Framework agnostic
(mocha, jasmin, cucumber)
Exists Since
0.6.0
Exists Since
0.6.0
Test Driven Development
TDD
Integration Testing
Do the parts work together?

Impractical to test every state.
Unit Testing
Does each part work
on it's own?
As Plugin
Test &
Commit
CI
As a User
would use
your system
Prezi, Notes, Example, Seed Projects, References, etc
available via here and @zeroasterisk

Thanks!
Full transcript