Download to read offline
Uploaded byMark Trostler
JUTE Workshop
This document discusses unit testing and the JUTE testing framework. It recommends writing small, simple tests and testing code early and often. It provides instructions on installing JUTE and writing tests, as well as running tests in the browser, with JUTE, and using different JUTE engines like Selenium. The goal is to write many tests to achieve 75% code coverage.
More Related Content
JUTE Workshop
- 1. Unit Test/JUTE Workshop MarkEthan Trostler trostler@yahoo- inc.com @zzoass
- 2. Minimize Your Pain •WriteSmall •Write Simple •Test Early •Test Often
- 3. Write Small –Write Simple •Isolate code to test •Loosely couple dependencies •Be obvious •Optimize last
- 4. Test Early –Test Often Test Now
- 5. Install JUTE •NodeJS (nodejs.org) •npm(curl http://npmjs.org/install.sh | sh) •JUTE (npm install jute –g) Yahoo’s: % yinsti –b test jute
- 6.
- 7. What To Test Your Function/Method ONLY!! Mock/Manage Dependencies: •Explicit •Internal •Environment
- 8. Run In Browser Loadup your HTML & let it fly!
- 9. Run Within JUTE- Browser % npmconfig set jute:<variable><value> %.... % yinst restart jute –g Load JUTE web UI & run some tests!
- 10. Run Within JUTE– Command line % jute_submit_test –test …. In parallel each captured browser runs every test
- 11. Run Within JUTE– Selenium Grab latest selenium-server-standalone % java –jar selenium… % jute_submit_test –sel_host<> --test … Serialized tests
- 12. Run Within JUTE– V8 % jute_submit_test –v8 <> --test … Serialized tests
- 13. Run Within JUTE– Selenium Grid % jute_submit_test –sel_host<> -- seleniums 5 --test … Tests in ‘seleniums’ chunks to each Selenium slave in parallel. Will block if you don’t have enough slaves!
- 14. Keep Writing ThoseTests!! Yahoo wants 75% coverage!
Editor's Notes
- #3 Get manager-speak out of the wayYou have heard all of this before from industry – from manager – from co-workers - there’s a reason: less pain for you – less pain for you managers – better codeWhy everyone all up in me about these things?You probably already agree it’s a good thingmanagers NEED you to succeedSmall = testableSimple = testable – minimize side effects – side effects harder to test – harder to capture – harder to explain
- #4 Lots of little – no bigPer function – test ONE THING AT A TIMEDo no create - injectIsolate what you want to testMocking out dependenciesCreating causes tight couplingClever comes later – if at all – don’t get cute or too clever – optimize LATER
- #5 NOWDon’t have to test first -
- #6 NOWDon’t have to test first -
- #7 NOWDon’t have to test first -
- #8 NOWDon’t have to test first -
- #9 NOWDon’t have to test first -
- #10 NOWDon’t have to test first -
- #11 NOWDon’t have to test first -
- #12 NOWDon’t have to test first -
- #13 NOWDon’t have to test first -
- #14 NOWDon’t have to test first -
- #15 NOWDon’t have to test first -