Home > Ask the Software Quality Experts > Software Testing and Quality Assurance Questions & Answers > Acceptance testing for websites
Ask The Software Quality Expert: Questions & Answers
EMAIL THIS

Acceptance testing for websites

Scott Barber EXPERT RESPONSE FROM: Scott Barber

Pose a Question
Other Software Quality Categories
Meet all Software Quality Experts
Become an Expert for this site


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


>
QUESTION POSED ON: 11 June 2008
I am the manager of a client acceptance testing team. We test internal desktop applications used by our employees, as well as websites that are used by our clients to look up account information and process transactions. For our internal applications, we follow a pretty strict testing methodology to avoid overlap with system testing. We test workflows and procedures to ensure that the product meets the users' needs. However, when it comes to testing our websites, we are probably doing a mini version of system testing because we don't really know exactly how our clients are using our website. For example, we know clients would not logically go the Web to look up one piece of information or process one transaction and logoff. I think that a true acceptance test would be replicating some of the scenarios. So that might be: Look up a price of a fund, look up past performance, look up stocks in the fund and then process a transaction. How would you differentiate system versus acceptance testing for a website? And when the website offers many possibilities, how does one really know how to replicate that behavior? Thanks for your time.

>
EXPERT RESPONSE

As far as I'm concerned, acceptance testing should be conducted by the people who you'd like to find the application acceptable -- without scripts or detailed instructions. I recognize this isn't always possible, but it is the only way to really know.

Lucky for you, it sounds like you have websites in production that you are regularly updating/enhancing. This gives you a *huge* advantage in that it is quite easy to find out what users actually do on your site. In fact, your IT or production support team probably already has weblogs that track (hopefully anonymously) user activities that you (or someone else) could parse to give you some insight into how your users are using the system.

Software testing resources:
Don't mistake user acceptance testing for acceptance testing

User acceptance testing that satisfies users and requirements

Usability testing vs. user acceptance testing

If these things are not being logged, it's simply a matter of setting that on the Web server. You may even have tools in house that parse the log files already. Again, your IT or production support staff will know. I recommend asking them what usage information they can provide for you, and if that information isn't adequate, see what you can do about getting a monitoring tool in place. If you need a tool, once again, you're lucky. Many are free. One of the most popular is Google Analytics, all you'll need is for developers to add a short snippet of code to the bottom of each Web page, then you can access analytics from anyplace you have an Internet connection and browse site usage data in near real time.

Good luck!


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


RELATED CONTENT
Software Testing and Quality Assurance
Should you retest closed defects during regression testing?
Common mistakes of new software testers
How to test an application's scalability, performance
Integration testing: Is it black box or white box testing?
Test strategy document vs. an acceptance test plan
The future of software testing
Quality assurance testing vs. user acceptance testing
Eliminating testing environment troubles
How to use tools for system integration testing
How to match the test environment to the production environment

User acceptance testing
Quality assurance testing vs. user acceptance testing
Overcoming user acceptance testing difficulties
Running UAT and system testing in parallel
Test metrics and use case coverage during testing
The benefits of user acceptance testing
The scope of user acceptance testing
Software testing fundamentals: User acceptance testing
Six functional tests to ensure software quality
The user acceptance testing (UAT) team is your ally
Usability testing vs. user acceptance testing

Advice from Scott Barber
Performance testing SOA
GUI automated testing projects
How to set up a test environment
Prioritizing software testing on little time
Software testing processes and development methodologies
Smoke and sanity testing
Automating regression test cases
Test plan and test strategy
User acceptance testing that satisfies users and requirements
Understanding performance, load and stress testing

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary



Search and Browse the Expert Answer Center
Search and browse more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.
Browse our Expert Advice



Software Quality - Software Maintenance, Software Requirements, Software Standards
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides enterprise IT professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective IT purchase decisions and managing their organizations' IT projects - with its network of technology-specific Web sites, events and magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Reprints  |  Site Map




All Rights Reserved, Copyright 2006 - 2008, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts