Test Engineering

Test Engineering Nigel Fernandes Software Design Engineer BookEazy Technologies Pvt. Ltd.

Why test ? To find bugs  To verify the specifications  To know the limits of the system  Good developer karma 

Types of Tests Unit Tests  Functional Tests  Automated Stress Tests  Load Tests  …and of course manual tests.

Who does the testing ? Developer Testing  Software Quality Testing  Beta User Testing 

It is really challenging ! Writing good tests is hard.  Avoiding ‘Happy Path’ tests is hard.  Avoiding Test Training is hard.  Budgeting for test development is hard  Maintaining tests is hard. 

Why should you care? Design Code Testing Time Estimate For Feature

What else? Code quality and Bugs  Code enhancements  Specification and Requirement changes  Sometimes there’s no other way 

The magic of Selenium “Selenium uses JavaScript and Iframes to embed a test automation engine in your browser”

Bits and Pieces Selenium Core  Selenium RC (love this)  Selenium IDE (damn cool) 

Selenium Architecture

Selenium Alternatives Watir  WebDriver  Jmeter 

Why Selenium rocks Cross browser support is the best available  Scaleable. Architecture supports multi-browser  parallelism JavaScript extendibility is just awesome  Selenium IDE for Firefox  Interactive Selenium RC  Down the line support 

Bunch of URL’s www.openqa.org  www.youtube.com [search  for GTAC 2007] tech.nigel.in  www.nigel.in  www.askAnayKamat.com  Email me at nigel@nigel.in

Test Engineering

by NigelFds on Oct 16, 2007

Accessibility

Categories

Tags

Upload Details

Usage Rights

3 Embeds 10

Statistics

Test Engineering — Presentation Transcript

http://www.techgig.com	5
http://www.brijj.com	3
http://www.slideshare.net	2