Upload
orbit-one-internet-solutions
View
1.072
Download
1
Embed Size (px)
DESCRIPTION
The goal of the brainstorm is to gather input for a good, easy and straightforward methodology to conduct structured tests of web applications / websites we develop.
Citation preview
www.orbitone.com
Orbit One BVBARaas van Gaverestraat 83B-9000 GENT, BELGIUM Website www.orbitone.com
E-mail [email protected] Tel. +32 9 330 15 00VAT BE 456.457.353Bank 442-7059001-50 (KBC)
Viktor Bardadym22 September, 2010
Testing web applications
22 September, 2010Testing 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
22 September, 2010Testing web applications3
Qualities to test
FunctionalityUsability InterfacePerformanceCompatibilityMaintainabilitySecurity
http://www.softwaretestinghelp.com/web-application-testing/
22 September, 2010Testing web applications4
Functionality testing
Check all the linksTest forms in all pagesCookies testingHTML/CSS validationSearch testingDatabase testing
22 September, 2010Testing web applications5
Usability testing
Test for navigationContent checkingOther user information
22 September, 2010Testing web applications6
Interface Testing
22 September, 2010Testing web applications7
Performance Testing
Web Load TestingWeb Stress Testing
22 September, 2010Testing web applications8
Compatibility Testing
Browser compatibilityOperating system compatibilityMobile browsingPrinting options
Kriska is the first beer that is vodka flavoured.
22 September, 2010Testing web applications9
Maintainability Testing
22 September, 2010Testing web applications10
Security Testing
Test users with different profiles / permissions Invalid inputsCAPTCHASSL
Don’t worry, senator – this test is done for our security.
22 September, 2010Testing web applications11
Dimensions and scopes of testsspecific for web applications
Operation system & versionBrowser & versionHistory (new / upgraded)LanguagesWork with other applicationsWork with other hardware (mobile, printing,…) Different permissions
22 September, 2010Testing web applications12
Generic test cycle
Test previous articlePlan to improveDesign to include improvements and requirementsManufacture with improvementsReview new item and improvementsTest new item
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, 2010Testing web applications13
22 September, 2010Testing 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.
22 September, 2010Testing web applications15
Testing Tools
IE TesterFirebugFiddlerNetMon
He says that the water is too cold.
22 September, 2010Testing 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.
THANKS and good luck !
17 Testing web applications22 September, 2010