How I learned to love and hate web-testing
fbb42a67-773d-47f7-b3e8-7b6493b9333f
 |
Presentation |
Introductory
Java Web Technologies
Room:
Lab 4
Timeslot:
18.09.08 11:45
Speaker: Thomas Ferris Nicolaisen
Good tools for automated web-testing have been around for quite some time, and many projects are starting to include them as a part of their build-process. We started using web-tests on Storebrand's online insurance-application back in autumn 2006, and the project is still supported by web-tests this very day. The talk gathers on experiences from this and various other Objectware projects, putting together a good bunch of experiences, recommendations, guidelines and hints for getting your project's web-testing in order.
Topics include:
- Why web-tests are evil!
- When should you NOT use web-tests
- How many web-tests should you maintain?
- How you can get the users to report bugs by writing tests for you
- Getting a CI/testing server to run the tests for you
- Combining web-tests with FitNesse acceptance testing
- Behaviour Driven Development using RSpec with web-tests
- Project testing strategy (and where web-tests fit in)
Outline
- Background
- A trip down memory lane in Storebrand: How did we get started?
- How we learned to love web-testing, and
- How we learned to hate it.
- Web-testing practices
- Testing the web and nothing but the web
- Black-box testing
- Acceptance/system testing
- Integration testing
- How to fit web-tests into the rest of your test-model
- How web-tests can give you good URLs and HTML design
- Running web-tests on the Continous Integration server
- Getting your users to help out: delivering bug reports with test-scripts
- Test fixtures
- Advanced web-testing
- Acceptence web-testing combining FitNesse and Selenium
- Behaviour-Driven Development with web tests (Selenium combined with the RPsec Story Framework)
- Web tests from a test strategy perspective
- How to scale (with Selenium Grid)
- Pitfalls
- Too many tests
- Too slow tests
- The tests break all the time!
- Some refactoring breaks all the tests
- Using web-tests for everything
- How to combine system testing with manual testing
- Capturing system requirements in web tests
- QA
Required experience:
No particular experience is strictly required, but having tried out some web- testing tool could be an advantage.
Expected audience:
- Web developers
- QA/testers
- People interested in testing in general
By attending this presentation, participants will learn...
- How to get started with web-testing
- How to keep doing it successfully
- How to use web-tests as part of an agile project
-
Thomas Ferris NicolaisenThomas holds a MSc degree in computer science from the University of Oslo and has been professionally developing Java applications since the spring of 2004. He maintains a passion for Java development, Agile methods and a wide range of open-source projects. During waking hours he works as a consultant for Objectware AS.