The document discusses testing methodologies for web applications. It recommends testing functionality, usability, interfaces, performance, compatibility, maintainability, and security. Specific tests are outlined, like checking links and forms, cookies testing, validation, searching, and working with different browsers, OSs, languages, and hardware. The document provides a sample test cycle involving preparing tests, creating report sheets, performing tests, and iterating tests until issues are resolved. Various testing tools are also listed.

1. www.orbitone.com
Orbit One BVBA
Raas van Gaverestraat 83
B-9000 GENT, BELGIUM
Website www.orbitone.com
E-mail info@orbitone.com
Tel. +32 9 330 15 00
VAT BE 456.457.353
Bank 442-7059001-50 (KBC)
Viktor Bardadym
22 September, 2010
Testing web applications

2. 22 September, 2010
Testing web applications2
Goal
To gather input for a good, easy and straightforward
methodology to conduct structured tests of web applications /
websites we develop.
"Le bon Dieu est dans le détail"
Gustave Flaubert

3. 22 September, 2010
Testing web applications3
Qualities to test
Functionality
Usability
Interface
Performance
Compatibility
Maintainability
Security
http://www.softwaretestinghelp.com/web-application-testing/

4. 22 September, 2010
Testing web applications4
Functionality testing
Check all the links
Test forms in all pages
Cookies testing
HTML/CSS validation
Search testing
Database testing

5. 22 September, 2010
Testing web applications5
Usability testing
Test for navigation
Content checking
Other user information

6. 22 September, 2010
Testing web applications6
Interface Testing


7. 22 September, 2010
Testing web applications7
Performance Testing
Web Load Testing
Web Stress Testing

8. 22 September, 2010
Testing web applications8
Compatibility Testing
Browser compatibility
Operating system compatibility
Mobile browsing
Printing options
Kriska is the first beer
that is vodka flavoured.

9. 22 September, 2010
Testing web applications9
Maintainability Testing

10. 22 September, 2010
Testing web applications10
Security Testing
Test users with different profiles / permissions
Invalid inputs
CAPTCHA
SSL
Don’t worry, senator –
this test is done
for our security.

11. 22 September, 2010
Testing web applications11
Dimensions and scopes of tests
specific for web applications
Operation system & version
Browser & version
History (new / upgraded)
Languages
Work with other applications
Work with other hardware (mobile, printing,…)
Different permissions

12. 22 September, 2010
Testing web applications12
Generic test cycle
Test previous article
Plan to improve
Design to include improvements and requirements
Manufacture with improvements
Review new item and improvements
Test new item

13. Test cycle
a) Prepare your test
 split web application / site in
modules/screens
 define concrete tests for each screen
(detailed description, for example
"enter a string of more than 100
characters in this textbox)
b) Make report sheet (using template)
 What customer/project
 FogBugz ticket number
 Who is the tester
 Version(s) of Windows / browser(s)
 Date & time
 Checksheet with tests
c) Do the first test, fill in the report sheet
 for each test + Green/Orange/Red +
comments
 at the end, add summary of the test
with general remarks. For example
"Everything works fine except things
related to iframe scrolling“
d) Put the report on SharePoint, and
inform the project manager / customer
/ developers to fix the orange and red
issues
e) Do the test for a second time, creating a
NEW report form
 iterations between c) – e) until all test
are successful
 in the real-world, more tests will be
added in each iteration
22 September, 2010
Testing web applications13

14. 22 September, 2010
Testing web applications14
Regression testing
Focuses on finding defects after a major change has occurred.
Specifically, it seeks to uncover regressions, or old bugs that
have come back.

15. 22 September, 2010
Testing web applications15
Testing Tools
IE Tester
Firebug
Fiddler
NetMon
He says that the water
is too cold.

16. 22 September, 2010
Testing web applications16
Testing fun
 1: Testing Festivals
 Internal professionals
 Case: A large high-technology organization asked its developers to
test applications for compatibility with the next version of
Windows. The test manager scheduled testing sessions in the lab
and sent notifications about the sessions to the developers. To
make the events fun, the test manager provided food and
beverages, thus earning the name "test fests" for the sessions.
 2: Preview Program
 External professionals
 Beta releases, release candidates.
 3: Conference Room Pilots
 End users
 The purpose of the Conference Room Pilot is to validate a
software application against the business processes of end users
of the software, by allowing end users to use the software to carry
out typical or key business processes using the new software.

17. THANKS
and good luck !
17 Testing web applications
22 September, 2010