Search

Test Your JavaScript

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

1 comments

Comments 1 - 1 of 1 previous next Post a comment

Post a comment
Embed Video
Edit your comment Cancel

Notes on slide 1

We’re talking about web-APPS, not just web-sites.

We’re talking about web-APPS, not just web-sites.

We’re talking about web-APPS, not just web-sites.

We’re talking about web-APPS, not just web-sites.

We’re talking about web-APPS, not just web-sites.

We’re talking about web-APPS, not just web-sites.

We’re talking about web-APPS, not just web-sites.

We’re talking about web-APPS, not just web-sites.

We’re talking about web-APPS, not just web-sites.

We’re talking about web-APPS, not just web-sites.

We’re talking about web-APPS, not just web-sites.

We’re talking about web-APPS, not just web-sites.

We’re talking about web-APPS, not just web-sites.

We’re talking about web-APPS, not just web-sites.

We’re talking about web-APPS, not just web-sites.

We’re talking about web-APPS, not just web-sites.

So, at what levels can we test?

stuff breaks
Broken stuff makes you look bad
So ... you fix it!

but then you add more features

the more stuff you have, the more likely it is to be broken WITHOUT YOU KNOWING

the more stuff you have, the more likely it is to be broken WITHOUT YOU KNOWING

where should you focus your testing efforts?

sure, focus on business value, BUT

think about what might be broken ...
the new stuff, ‘cos you changed it
the old stuff, ‘cos you’re not looking at it
ie. EVERYTHING

so, you get MORE testers

but manual regression testing costs money, and takes lot of time

but manual regression testing costs money, and takes lot of time

manual testing

manual testing

manual testing

manual testing

manual testing

manual testing

manual testing

manual testing

manual testing

automated testing provides the confidence needed to keep moving forward

So, at what levels can we test?

test the whole thing, end-to-end

At the other extreme: test small components

Big because they require a lot of work to create
Powerful because they exercise many components of the system at once
Convincing because they prove that the components hang together
Slow because they exercise all the infrastructure
In-exact because it can be hard to find the cause of a failure
High-maintenance because many things may require the test to be modified

Big because they require a lot of work to create
Powerful because they exercise many components of the system at once
Convincing because they prove that the components hang together
Slow because they exercise all the infrastructure
In-exact because it can be hard to find the cause of a failure
High-maintenance because many things may require the test to be modified

Big because they require a lot of work to create
Powerful because they exercise many components of the system at once
Convincing because they prove that the components hang together
Slow because they exercise all the infrastructure
In-exact because it can be hard to find the cause of a failure
High-maintenance because many things may require the test to be modified

Big because they require a lot of work to create
Powerful because they exercise many components of the system at once
Convincing because they prove that the components hang together
Slow because they exercise all the infrastructure
In-exact because it can be hard to find the cause of a failure
High-maintenance because many things may require the test to be modified

Big because they require a lot of work to create
Powerful because they exercise many components of the system at once
Convincing because they prove that the components hang together
Slow because they exercise all the infrastructure
In-exact because it can be hard to find the cause of a failure
High-maintenance because many things may require the test to be modified

Big because they require a lot of work to create
Powerful because they exercise many components of the system at once
Convincing because they prove that the components hang together
Slow because they exercise all the infrastructure
In-exact because it can be hard to find the cause of a failure
High-maintenance because many things may require the test to be modified

Big because they require a lot of work to create
Powerful because they exercise many components of the system at once
Convincing because they prove that the components hang together
Slow because they exercise all the infrastructure
In-exact because it can be hard to find the cause of a failure
High-maintenance because many things may require the test to be modified

Big because they require a lot of work to create
Powerful because they exercise many components of the system at once
Convincing because they prove that the components hang together
Slow because they exercise all the infrastructure
In-exact because it can be hard to find the cause of a failure
High-maintenance because many things may require the test to be modified

Plentiful because they’re cheap
Quick because they’re low-overhead
Focused because they point the finger directly at the cause of failure
Resilient because they’re isolated from unrelated parts of the system
Limited because, individually, they don’t test very much

Plentiful because they’re cheap
Quick because they’re low-overhead
Focused because they point the finger directly at the cause of failure
Resilient because they’re isolated from unrelated parts of the system
Limited because, individually, they don’t test very much

Plentiful because they’re cheap
Quick because they’re low-overhead
Focused because they point the finger directly at the cause of failure
Resilient because they’re isolated from unrelated parts of the system
Limited because, individually, they don’t test very much

Plentiful because they’re cheap
Quick because they’re low-overhead
Focused because they point the finger directly at the cause of failure
Resilient because they’re isolated from unrelated parts of the system
Limited because, individually, they don’t test very much

Plentiful because they’re cheap
Quick because they’re low-overhead
Focused because they point the finger directly at the cause of failure
Resilient because they’re isolated from unrelated parts of the system
Limited because, individually, they don’t test very much

Plentiful because they’re cheap
Quick because they’re low-overhead
Focused because they point the finger directly at the cause of failure
Resilient because they’re isolated from unrelated parts of the system
Limited because, individually, they don’t test very much

Plentiful because they’re cheap
Quick because they’re low-overhead
Focused because they point the finger directly at the cause of failure
Resilient because they’re isolated from unrelated parts of the system
Limited because, individually, they don’t test very much

JavaScript unit tests run really FAST!

Talk about why

Cross-browser, cross-version testing
Mainly for libraries - you probably don’t need it

4 Favorites & 1 Event

Test Your JavaScript - Presentation Transcript

  1. Test your JavaScript Mike Williams, Rob Mitchell at Web Directions South ’09
  2. For the love of God, Test your JavaScript (automatically) ... or suffer the consequences.
  3. Browser
  4. Browser Web/Application server
  5. Browser Web/Application server Framework Lib Lib
  6. Browser Web/Application server Framework Lib Your code Lib
  7. Browser Web/Application server Framework Lib External Your systems code Lib
  8. Browser Web/Application server Framework Lib External Your systems code Lib circa 2000
  9. Browser Web/Application server Framework Lib External JS Your systems code Lib circa 2000 2004
  10. Browser Web/Application server Framework Lib Lib Your External JS Your systems code Lib code Lib circa 2000 2008 2004
  11. Browser Web/Application server Framework Lib Lib Your External Your systems code Lib code Lib Mature test automation Not so much tools and practices
  12. Why test?
  13. Why test?
  14. Variety
  15. Variety
  16. The problem with success ↑ risk of (undetected) #fail time, features, users →
  17. The problem with success ↑ risk of (undetected) #fail time, features, users →
  18. The problem with success ↑ risk of (undetected) #fail time, features, users →
  19. Where to start?
  20. what will cause the most damage, if it breaks?
  21. what’s most likely to be broken?
  22. Manual regression testing
  23. Manual regression testing
  24. Manual regression testing $
  25. Manual regression testing $ ⌛
  26. Cost of testing
  27. Cost of testing quarter month fortnight week few days day Release frequency →
  28. Cost of testing manual tests ↑ Testing Cost, Delay quarter month fortnight week few days day Release frequency →
  29. Fear
  30. Fear Disincentive to
  31. Fear Disincentive to ‣ add features
  32. Fear Disincentive to ‣ add features ‣ refactor
  33. Fear Disincentive to ‣ add features ‣ refactor ‣ release!
  34. Automation
  35. Cost of testing
  36. Cost of testing ↑ Testing Cost, Delay quarter month fortnight week few days day Release frequency →
  37. Cost of testing manual tests automated tests ↑ Testing Cost, Delay quarter month fortnight week few days day Release frequency →
  38. Confidence
  39. Test strategy
  40. Browser Web/Application server Framework Lib Lib Your External Your systems code Lib code Lib
  41. Browser Web/Application server Framework Lib Lib Your External JS Your systems code Lib code Lib “End-to-end” test
  42. Browser Web/Application server Framework Lib Lib External systems Lib Lib Unit tests
  43. Component tests (assorted) Browser Web/Application server Framework Lib Lib Your External JS Your systems code Lib code Lib
  44. End-to-end tests
  45. End-to-end tests
  46. End-to-end tests Big
  47. End-to-end tests Big Powerful
  48. End-to-end tests Big Powerful Convincing
  49. End-to-end tests Big Powerful Convincing ...
  50. End-to-end tests Big Powerful Convincing ... Slow
  51. End-to-end tests Big Powerful Convincing ... Slow In-exact
  52. End-to-end tests Big Powerful Convincing ... Slow In-exact High-maintenance
  53. Unit tests
  54. Unit tests
  55. Unit tests Small
  56. Unit tests Small Quick
  57. Unit tests Small Quick Focused
  58. Unit tests Small Quick Focused Resilient
  59. Unit tests Small Quick Focused Resilient ...
  60. Unit tests Small Quick Focused Resilient ... Limited
  61. Speed Annoyingly slow Very fast Unit test End-to-End test
  62. Speed Annoyingly slow ↑ Execution Time Very fast Unit test End-to-End test
  63. Balance many fast tests a few slow tests
  64. Favour FAST tests over SLOW tests
  65. The Healthy Test Pyramid manual few end-to-end some (automated) slow the stuff in between (automated) fast! “unit” (automated) most
  66. Tools
  67. Browser Web/Application server Emulator Framework Lib Lib Your External Your systems code Lib code Lib Test scripts
  68. Browser Web/Application server Framework Lib Lib Your External JS Your systems code Lib code Lib Browser Driver Test scripts
  69. Browser Lib Your JS code Lib Unit-test framework Test scripts
  70. Browser Emulator Lib Your JS code Lib Unit-test framework Test scripts
  71. pls can we haz demo!
  72. Testability
  73. Testability • Coherent modules
  74. Testability • Coherent modules • Coherent tests
  75. Testability • Coherent modules • Coherent tests • Unobtrusive JavaScript
  76. Testability • Coherent modules • Coherent tests • Unobtrusive JavaScript • Write the tests first!
  77. Write the tests first! Testability Good Design
  78. Build integration • Very tool-specific • Trickiness: • Stopping and starting servers • Stopping and starting browsers
  79. TestSwarm TestSwarm server Test scripts
  80. What now? JavaScript test frameworks Browser Drivers - Screw.Unit - Selenium-RC - QUnit - Watir - JSSpec - WebDriver - YUI Test - unittest.js Browser Emulators - JsUnit - HtmlUnit - and lots more ... http://delicious.com/mdub/javascript+testing

+ mdubyamdubya, 1 month ago

custom

513 views, 4 favs, 1 embeds more stats

an introduction to automated testing of JavaScript- more

More info about this document

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Go to text version

  • Total Views 513
    • 460 on SlideShare
    • 53 from embeds
  • Comments 1
  • Favorites 4
  • Downloads 16
Most viewed embeds
  • 53 views on http://www.webdirections.org

more

All embeds
  • 53 views on http://www.webdirections.org

less

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel
File a copyright complaint
Having problems? Go to our helpdesk?

Categories

Tags

Groups / Events

-->
Search
RSS Feed
What's new?

© 2009 SlideShare Inc. All Rights Reserved