This document summarizes a presentation about using Behavior-Driven Development (BDD) with Pavlov and QUnit for natural language UI testing. Pavlov is a behavioral API over QUnit that allows writing tests using natural language. The presentation demonstrates using Pavlov to test a login form according to a spec written in natural language. It also discusses Pavlov's features, future plans for cross-browser testing and framework independence, and provides links to example code and slides.

1. jQuery Conference: San Francisco Bay Area 2011
Natural Language UI Testing
Using
Behavior-Driven Development
With Pavlov and QUnit

2. Eric DeLabar
• Solutions Architect at Trifecta Technologies
• http://www.trifecta.com/

3. What’s Behavior Driven
Development?
(BDD)

4. “BDD is a second-generation, outside-in,
pull-based, multiple-stakeholder, multiple-
scale, high-automation, agile methodology.
It describes a cycle of interactions with
well-defined outputs, resulting in the
delivery of working, tested software that
matters.”
-Dan North

5. What is Pavlov?

6. Behavioral API over QUnit
by Michael Monteleone
http://github.com/mmonteleone/pavlov

7. The Goal:
The login form
should progressively enhance a form by id.
should hide a field label when the field has focus.
should show a field label when the field is empty when the cursor leaves.
should keep a field label hidden when the field is not empty when the cursor leaves.
should validate that the email field is valid when the cursor leaves.
should submit the form when the user clicks the Join button.
should submit to the action URL of the form with an AJAX POST.

8. Format spec for Pavlov:

9. Spec HTML (head)

10. Spec HTML (body)

11. First Test

12. Make it Pass

13. Second Test

14. Make it Pass

15. Third Test

16. Make it Pass

17. Fourth Test

18. Make it Pass

19. Fifth Test

20. Make it Pass

21. Sixth Test

22. Make it Pass

23. Seventh Test

24. Adding Mockjax

25. Make it Pass

26. Finished!

27. What’s Next?
• Add a new Feature?
• Make it better, faster, lighter?
• Fix a bug?
• Cross-browser testing?

28. Real World Usage
• Major National Corporation
• 3 different mobile web applications
• 3 separate schedules & deployment dates
• Shared custom library + jQuery Mobile

29. Other Features
• Custom Assertions
• Expected Exceptions
• Run from Command Line or CI Server

30. Future of Pavlov
• Testing-framework-neutral refactor in-
progress
• coming soon: support for YUI2 and 3
• Try it now: framework-agnostic branch on
GitHub
• Ironically enough, needs more test
coverage

31. Materials
• Example Code on GitHub:
https://github.com/edelabar/jqconf2011-pavlov-talk
• Slides on SlideShare:
http://slidesha.re/fOmeBF

32. Questions/Comments?
• Twitter @edelabar
• Email: edelabar@gmail.com
• SpeakerRate: http://spkr8.com/t/7239