Kris

Is there an application that will test a WAP service across the full range of WAP phones?

On 18:47:33 7 October 2000 kris wrote:
>Welcome to e-consultancy.com and the technology forum. My
>first posting is actually not very technical, but is very
>important all the same. It involves User Acceptance
>Testing for E-commerce sites.
>
>After building a fair number of corporate e-commerce sites
>myself, I have realised one of the most fundamental things
>overlooked when developing a new
>e-commerce web site is user acceptance testing. Many web
>developers underestimate what is involved in testing an
>e-commerce site from a user's perspective.
>
>System testing and load balancing are important. But if
>your site is not user friendly or does not meet the
>expectation of your audience, it can cost your new
>Internet business dearly.
>
>The following steps need be taken to ensure that you have
>successfully tested your site:
>
>1. Complete all system testing and quality assurance (QA)
>by your development team before commencing User Acceptance
>Testing. This allows the testers to focus on usability
>issues and not technical defects.
>
>2. Use ordinary online users to test your site. Do not use
>your development or production team. This ensures people
>testing the site are new to your online shopping
>experience. First impressions are important.
>
>3. Construct a UAT project plan that is independent of
>your development plan. This guarantees the testing process
>can be effectively managed by a testing co-ordinator
>without interference from other project tasks.
>
>4. Write a testing plan explaining in plain English what
>needs to be tested and how. Construct testing routines for
>every page in your site, detailing expected results of all
>the functionality. From these the tester can easily
>identify the appropriate outcome from every action
>response.
>
>5. Test on all target platforms and browsers. These should
>be outlined in the site's technical specification. But
>make sure they are listed again in your testing plan
>document.
>
>6. Install change control software on your staging server
>and incorporate it into your testing routines. This means
>listing all pages and functionality in the system so
>testers can easily enter defect reports or usability
>issues. Note: Make sure you allow an adequate amount of
>time in your testing project plan for the change control
>process.
>
>7. A senior project lead and not the testers should
>conduct prioritisation of defect fixing. This ensures
>change control tasks are allocated to the right people.
>The project lead should also make sure the development
>team change the status of a defect once it is fixed.
>
>8. Conduct at least three rounds of testing. This ensures
>after change control has been completed any 'fixes' do not
>have an impact on any other
>functionality on the site.
>
>9. After UAT is completed and the site is deployed.
>Conduct a final full loop test on the 'live' server
>(password protected only) with technical and
>production staff, to make all defects in the change
>control system are completed and signed off.
>
>If you have any feedback or questions please post a reply
>or email me at