What the heck is that bar over there?

(1)

(2)

(3)

(4)

(5)

(6)

(7)

(8)

i. Some real-life besserwissening

ii. Technology 1: Selenium for web-testing

iii. Technology 2: Hudson for Continous Integration

(9)

thomafni

MSc from ifi spring 2006 inf5750 spring 2005

Blog here: http://tfnico.blogspot.com

(10)

hisp.info

svn co http://www.hisp.info/svn/trunk/dhis-2/ mvn install

building... ...lotsa deps tests are running.. ... and running... oi, a test failure! : Failed tests:

testExport(org.hisp.dhis.importexport.ixf.IXFExportServiceTest) jaja, -Dmaven.test.skip=true

still on webwork 2.2.6? tsk, tsk, well so are we anyway mvn eclipse:eclipse and import into Eclipse..

(11)

•_{Active mailing lists} •_{Improved Wiki}

•_{Code looks nice} •_{An active Trac} •_{Demo up!}

(12)

(13)

BEAUTIFUL! Well done.

(14)

(15)

(16)

*Disclaimer:

This presentation was originally made for Storebrand developers (in Norwegian).

(17)

Warmup

 _{Web developers?}  _Tried..  _JUnit  _FIT(nesse)  _Watir  _Selenium

(18)

A trip down memory lane

January: Selenium is released

Quickly gains attention through conferences, articles, etc

(19)

A trip down memory lane

October: Storebrand starts using Selenium tests

• Verifying use-cases • Regression testing

• Basis for performance tests

(20)

A trip down memory lane

Selenium development hibernation (only 1 release)

November/December: Storebrand’s tests are freshed up

(21)

A trip down memory lane

Storebrand still runs Selenium tests

Selenium popularity increases (1.0 beta released)

2008

”Google has 51k Selenium tests running accross 50 different teams”

(22)

Why test?

People are slow! Tests can be automated (and monitored) Errors in existing code introduced

(regression_tests) Verify functionality (use-cases) Handy for debugging

(23)

Why test web?

 _{Some things you can’t test with JUnit (easily)}

 _JSP

 _{HTML/Web-design}  _JavaScript

 _{Navigation/urls (struts.xml)}

(24)

Some architecture

Web

JSP JSP JSP JSP

Controller Controller Controller Controller

(25)

Some test architecture

Web

JSP JSP JSP JSP

Service Service

JUnit JUnit JUnit ?

(26)

Web-testing tools

Pros Cons Selenium (JS-engine) Can test JS Good Recorder Browser dependant Watir (Ruby) Powerful language Runs native IE New language Browser dependant HtmlUnit (Java) Mature

Virtual browser buffer

(27)

Selenium

 _{Selenium IDE (Firefox plugin)}  _{Selenium Core}

 _{Remote Control}

(28)

Good things about Selenium

 _{Active community}

 _{Scaringly easy}

(29)

A normal day in the

web-testers life

 _{Do a quick demo on local DHIS2}  _{(Or on the demo site)}

(30)

maven-selenium-plugin

 _{take it for a spin}

(31)

What can go wrong

 _{Too much time}

 _{Too much ”dill”}

 _{Tests break without anything being wrong}

(dialog boxes, browser upgrades)

 _{Too many tests}

 _{Too long, slow tests}

(32)

Remedies

 _{Use it, and get help}  _{Good urls, good id’s}  _{Test suites:}

(33)

Don’t test these

 _{Performance (unøyaktig måling)}  _{Data (too static)}

 _{Business rules (imprecise)}  _{Integration (too slow)}

(34)

More tips

 _{Push tests ”downward”}  _{Be pragmatic}

 _{Don’t test everything with Web/GUI-tests}  _{Have a strategy}

 _{Make bugreporters record traces when they report errors}

Web

JSP JSP JSP JSP

Service Service JUnit

JUnit JUnit ?

(35)

Testing Strategies

 _Selenium? --- _Fit?

--- _TestNG?

(36)

---Testing Strategies

 _Selenium? --- _Fit? --- _TestNG? --- _JUnit? ---No data Data No

environment Environment Location

Unit test Fast (1-5) n/a Fast (1-5) n/a

Service test Fast (1-5) Slow (2-5) Fast (1-5) Slow (2-5)

System test Slow

(37)

(38)

Questions to you

 _{Should we run clean install before every}

commit?

(39)

Continous Integration

 _{Don’t run the tests yourself}

(40)

Take it for a spin

 _{Show off hudson locally}

(41)

Continous Integration

 _{Let the machines do the testing}

 _{Earliest possible feedback!}  _{The build is broke!}

 _{What’s broken?}  _{Who broke it?}

(42)

Continous Integration

 _{Continuum (from the Maven lads)}  _{Hudson (Koshuke, the devil)}

 _{CruiseControl (good old)}  _{Bamboo (Atlassian)}

(43)

Things to consider

 _{One product, one build?}

 _{(you could build site..)}

 _{Lots of different things to test}  _{Many testing frequencies}

 _{Each commit}  _Hourly

(44)

My advice

 _{For every combination (you want to do)}  _{Make a job: build goal plus frequency}

 _{2 minute build}  _{10 minute build}  _{database-integration tests}  _web-tests  _{every-2-hour-integration tests}  _{nightly site/snapshot}

(45)

Broken or unstable?

 _{Is it broken if only 1 test doesn’t run?}

 _{What does broken mean?}

 _{Is that test releavant to all the other modules?}

(46)

Broken or unstable?

 _{Make the CI see the difference}

 _{Hudson and Bamboo shows new test-failures}  _{Yellow versus green builds}

(47)

Conclusion

 _Today:

 _{Install Selenium IDE}

 _{Next weeks:}

 _{Maintain a handful of tests}

 _{When/if you learn to love them}

(48)

(49)