True web site collaboration! ™
 
 
Web application development

Web based applications can put a heavy strain on the quality assurance aspect of product development. There is no easy way to capture the errors brought to light during the quality control process as you go through the test procedures for the product. Most web based products, be it banking applications, shopping carts, content customization or document management, have a complex workflow which is heavily dependent on the context of the current user and browser. Errors sometimes can not be reproduced without exact reproduction of the context they are in, which can be very difficult. Often the quality tester and the developer resort to screen captures, written notes and personal discussions to try to determine what went wrong and what it actually looked like in the browser.

With Zezame these cumbersome methods become a thing of the past. Testing of dynamic web applications is easy within Zezame, where each dynamic web page is automatically captured on the server, together with the POST data that produced it. Storing test runs becomes a snap and if you get an error, just show the developers what went wrong, as the error producing pages are kept for as long as you want them. Attaching comments on the page to highlight cause and effect is easy and you can hold a discussion with the developer "on the page" using the comment feature of the notes. Completed test suites can be kept to show that each aspect of the system has been tested as required.

If you are the external web development team, fighting ever shortening lead times to the target go live date as your client gets increasingly concerned, you can 'buy' time by using Zezame to rapidly highlight issues with your colleagues to spend time on finding the solution rather than having to go into a huddle to see what the problem is. How much is it worth to you with more rapid sign off to be able to hit those deadlines?

Equally if you are the client how much cost and frustration can you save by being able to show your developers exactly where and how their application is failing. Bringing new developments in on time and avoiding cost overruns will make that overstretched budget go further.