Download as PDF, PPTX
![Unit Testing Framework
describe('Array', function(){
describe('#indexOf()', function(){
it('should return -1 when not present', function(){
[1,2,3].indexOf(5).should.equal(-1);
[1,2,3].indexOf(0).should.equal(-1);
})
})
})](https://image.slidesharecdn.com/01intro-131210122359-phpapp02/85/Introduction-To-Web-Application-Testing-18-320.jpg)
![Unit Testing Framework
describe('Array', function(){
describe('#indexOf()', function(){
it('should return -1 when not present', function(){
[1,2,3].indexOf(5).should.equal(-1);
[1,2,3].indexOf(0).should.equal(-1);
})
})
})](https://image.slidesharecdn.com/01intro-131210122359-phpapp02/75/Introduction-To-Web-Application-Testing-18-2048.jpg)
Uploaded byYnon Perek
Introduction To Web Application Testing
The document discusses web application testing, highlighting challenges such as diverse browsers and devices, and advocating for automated testing to enhance feedback and reduce errors. It covers various testing types including unit tests and system tests, along with recommended tools and frameworks like Selenium and Mocha. The document emphasizes the importance of continuous integration, code coverage, and balancing different types of tests for effective software development.
More Related Content
Similar to Introduction To Web Application Testing
Introduction To Web Application Testing
- 1. Web Application Testing YnonPerek ynon@ynonperek.com http://ynonperek.com
- 2. Agenda • Developing forthe web. Why is it hard? • What can you test? • Testing architecture
- 3. Why is ithard?
- 4. Why is ithard? • Many different browsers • Many different devices
- 5. Automatic testing is youronly way out …
- 6. Imagine … • Shortfeedback loop on changes • Reduce human mistakes • TDD
- 7. Types of Tests Unittests http://johnny.github.io/jquery-sortable/ System tests
- 8. Unit Tests • Duringdevelopment, for the developer • Instant feedback • Future aware • Easy to maintain
- 9. System Tests • Testsentire system • For the client • Easy to write
- 10. What Can YouTest? • Everything … • But you probably shouldn’t
- 11. What Should YouTest? • Past bugs • Intended behaviour • Edge cases
- 12.
- 13.
- 14.
- 15.
- 16.
- 17. Unit Testing Framework •Provides structure to test code • Easy to report failures • Written in JavaScript
- 18. Unit Testing Framework describe('Array',function(){ describe('#indexOf()', function(){ it('should return -1 when not present', function(){ [1,2,3].indexOf(5).should.equal(-1); [1,2,3].indexOf(0).should.equal(-1); }) }) })
- 19.
- 20. Available Frameworks • Mocha •Jasmine • QUnit • http://en.wikipedia.org/wiki/ List_of_unit_testing_frameworks#JavaScript
- 21. System Testing Tools •Control an automatic browser • Can use any programming language
- 22. System Testing require "selenium-webdriver" ! driver= Selenium::WebDriver.for :firefox driver.navigate.to "http://duckduckgo.com" ! element = driver.find_element(:name, 'q') element.send_keys "Hello WebDriver!" element.submit ! puts driver.title ! driver.quit
- 23. System Testing Tool •We’ll use selenium • It’s stable and flexible • Really easy to automate
- 24. Test Runners • Runtests, report errors • Used from command line or IDE • Available options: • Karma, Chutzpa, js-test-driver
- 25. Continuous Integration • Checkoutlatest from source control • Run all tests • Report failures
- 26. Continuous Integration • Travis •Jenkins • TeamCity
- 27. Code Coverage • %of the code being tested • 70-80% is good • Istanbul is the tool
- 28.
- 29. Balancing Tests • Fewsystem / scenario tests • Many unit tests
- 30. Resources • Chuzpa screencastfor VS2012: http://www.youtube.com/watch? v=meJ94rAN7P8 • Miško Hevery on Unit Tests (google tech talks): http://www.youtube.com/watch? v=wEhu57pih5w
- 31. What Next • Writeunit tests • Write functional tests • Deploy a CI • Set up coverage and test reports
- 32. Ready? Let’s Go! •Ynon Perek • http://ynonperek.com • ynon@ynonperek.com