testing in web time presented by mike salisbury
DESCRIPTION
TRANSCRIPT
Testing in Web Time
Presented by Mike Salisbury
of logicalQA
Who Am I?
7 Years in Software Training, Installation and Support
3 Years in QA, Specializing in Web based applications
2 months as a QA Consultant to the software industry
My Definition of Web QA?
Provides Outside Objectivity
Provides Assurance of Software Stability
Verifies the Software is Useable
Confirms that the Software Meets Business Objectives
Why QA?
Your business depends on it!Recent Study:
50% of users could not complete on-line purchases assigned!
Only 20% of the development teams surveyed implemented formal testing prior to live launch!!!
www.metagroup.com 12/31/01
QA ensures the critical Website functions are useable and error free
QA Misconceptions
I can release bug fixes to the Web in a second. Proper steps is to do another release cycle.
Branch Code Tree
Your customers should not be your testers. Catch the bugs before you go live.
Fix Problem Code Release Code to Test
Test Code Fix
Regression Test Release Live Test Live Merge Code Tree
Re-fix / Re-test Bug
QA Misconceptions
Coders Generally Testers Generally
My developers can test their own code.
Model system design Focus on how it can
work
Model user behavior Focus on what can
go wrong
Coders + Testers = High Quality Software
QA Misconceptions
QA will help you:
Fix Bugs Earlier Fix Bugs Faster Fix More Bugs Produce High Quality Web Sites
I can’t afford a QA Tester!
Achieving Superior QA in Web Time
2 big challenges in the Web QA world Lack of Client Side Control Rapid Software Development Lifecycle
Achieving Superior QA in Web Time
Superior Web QA is: QA Involvement in Every Phase of Development Prudent Risk Based Test Planning Testers Knowing Customer Behavior Correct Use of Issue Tracking System QA Gaining Developers Trust
Testing a Sample Web Application
Login Screen Test Cases
Smoke / Functionality Tests
Tests to make sure the app is stable by: (Smoke) Is the page loading properly?
Tests to make sure app works as designed by: (Functionality) Logging in using a valid login and password
Is the login referencing correct account? Is there a DB capturing my login information?
• Is the DB information correct?
Is the user proceeding to the correct page after logging in?
Usability Tests
Tests to verify my mom can use the page Can the user easily tell what they need to do? Are the size of the entry fields appropriate? After logging out from the system:
Can the user easily login again? After a failed login attempt:
Can the user easily identify what the error is? Can the user correct the information entered?
Usability Errors
Entry fields not large enough
Need to Re-enter Information after failed login
Usability Errors
Login using incorrect login or password: Error message not specific
Boundary Tests
Tests for app error handling capabilities by: Inserting large data values
Login / Password accept 100 characters or more? Forcing null data values
Click login without entering anything. Entering unexpected data values
Enter letters in numbers fields. Possible to set up duplicate logins?
Boundary Errors
Login using letters in fields expecting numbers: Error messages confusing for user
Boundary Errors
Force login of 100 characters Bonanza! Exception Page!
Boundary Errors
Login using NULL data values
Boundary Errors
NULL test results in administration access!
Browser Tests
In all popular browsers, test for: Graphic / page rendering issues Mouse over actions Link actions
What browsers are popular? IE 5.0 – 6.0 command 80% market share NS 4.7 a distant second The rest – know your customers
ISP / Operating Systems Tests
Can I login using AOL?Can I login using a Mac?Sample Test Lab for Web Site
Win 95 with IE 4.0 and NS 4.0 Win 98 with IE 5.0, NS 4.7 and AOL 5.0 Win 2000 with IE 5.5 and AOL 6.0 Win XP with IE 6.0, NS 6.2 and AOL 7.0 IMac with current IE and NS
Browser Error
Cannot click the ‘New User?’ icon in NS 4.7 Icon links properly in all other browser versions
Main System Tests
Cookie Testing: Test for failure by: Refuse to accept all cookies Refuse to accept some cookies Corrupt / delete cookies Data encryption in cookies
Back Button Test: Test for failure by: Login correctly Click back button Login again
Main System Tests
Session Testing Will system log user out after period of inactivity?
What if user is in the middle of a transaction?
Login same user, 2 different browser instances: Can the system handle this?
Do the results fit with the site design?
Close browser while logged in: Reopen and bring up home page:
Does the user have to login again?
Main System Tests
Disable back end database: Does the login page still appear? Does the user get an understandable error
message?
Client side JavaScript error trapping: Login with JavaScript disabled in the browser.
Does the user get an understandable error message?
Main System Tests
Client Side JavaScript Error Trap
Additional QA for Web Applications
Other Web Testing Considerations Browser Plug-ins User Bandwidth Server Load Performance
Other Test Classes Regression Testing Pre – Post Release Testing
In Closing
QA Resources www.stickyminds.com www.qaforums.com Books by Hung Nguyen
Testing Computer Software Testing Applications on the Web
Mainebiz Magazine – February Issue Article on QA in Maine
Good QA won’t catch everything, but it will catch the important things.
QA Joke
How many Quality Assurance Engineers does it take to change a light bulb?
NONE! They just report it is out!
THANK YOU!
Questions / Discussion Time