Billups Design

Testing, QA, and Bug Fixes

Mission critical final steps that are often overlooked.

Usability Testing

Quickly and cost-effectively receive feedback from key users. Usability testing only requires 5 or 6 users to be extremely effective at finding and validating problems. A great investment, especially during down-times in the economy – maximize what you have!

Browser Testing

Billups Design can analyze your existing site’s performance across various browsers and platforms and help you get it performing well on all of them. Does the layout maintain its integrity? Do images all present consistently? Are functionals performing identically in any browser? We helped invent what will soon be the world’s greatest cross-browser testing tool, MeerMeer (soon to be introduced as Browser Lab), so we know a lot about this important field.

Unit/System Testing

Ensuring user input produces the appropriate output at the unit (single task) and system (web site) levels. No actual users are typically involved in this type of systematic testing, and scripts can be used to quickly trap errors, i.e. broken links, markup that does not validate, accessibility, seo elements, etc.

Integration Testing

With the integration of multiple systems and domains there is a need to ensure that input from the system will produce the expected output at the integrated system(s). This can range from logging into an API all the way to performing sample transactions in an ecommerce application.

Volume Testing

The system must be tested to ensure it can handle the projected maximum load that will be placed upon it when live. This testing involves softare, hardware and connectivity.

Regression Testing

Once bugs are established and fixed there needs to be testing to ensure the fix is now correct, and that no new bugs have been introduced into the system.

User Acceptance Testing (UAT)

When a system is successfully working per its requirements it must be tested with the actual administrators (the client staff) of the system. Any failures that are outside of the requirements/scope that need to be fixed are to be discussed as either pre or post launch initiatives with adjustments to the scope document.

Bugs and Fixes

The basic system for tracking bugs and their related fixes is through a simple database or grid, as follows:

• ID of bug
• Status of bug (new, in-progress or resolved)
• Priority of bug:
  • Red = non-functionality, must be fixed
  • Amber = interference, fixed before live
  • Green = annoyance, fixed before live if time allows