1. Selenium Conference 2013, Boston
Cross-browser
unit testing JavaScript
Alan Parkinson
@alan_parkinson #seconf

2. You want the Truth?
You can’t handle the Truth

3. You don’t need to run your Selenium
Test suite with every browser*
The Truth

4. • No visual testing
• Low JavaScript code coverage
• Costly to improve coverage
Rendering Compatibility
JavaScript/DOM Compatibility
What do we achieve?

5. • JavaScript and DOM compatibility
• Good code coverage
• Reusing a development artifact
Run all JavaScript unit tests cross browser
Simple Answer

6. • Average Test: 8 Seconds
• Test Suite: 5 minutes
• Average Test: 0.1 seconds
• Test suite: 11 seconds
Functional Tests
JavaScript Unit Tests
Looking at the numbers

7. Do we meet our compatibility objective?
Code Coverage has use

8. • Too many JavaScript files
• Order of loading files
Not everything will be picked up by Unit Tests
*The qualifier
Only run critical functional tests cross-browser

9. JavaScript Test Runners
Reusing your Selenium infrastructure

10. • Testing Framework Agnostic
• Continuous Integration
• Code coverage with Instanbul
• Launch Browsers
• Manually connect browsers
Spectacular Test Runner for JavaScript
Real Browsers
Karma

11. • Connects Remote WebDriver Instances
• Selenium Grid 2
• Supports Desired Capabilities
Reusing your Selenium Infrastructure
Karma WebDriver Launcher

12. Karma in action

13. • Code Coverage
• Feedback time
• Meeting our objective - Compatibility
• Karma Runner
• Reuse your existing Selenium WebDriver infrastructure
• Use code coverage to validate the majority of your code is
compatibility tested.
Functional tests have poor performance:
Cross-browser unit test JavaScript
Summary

14. https://karma-runner.github.com
https://github.com/hindsightsoftware/karma-webdriver-launcher
https://github.com/hindsightsoftware/karma-webdriver-example
Thank you
Alan Parkinson
alan.parkinson@hindsightsoftware.co.uk
@alan_parkinson