What do we test?
All projects share a set of common tests, but some tests depends on the project.
Types of Performance Testing
- Page Display in various browsers
- Each component validation
- Server configuration and load time: header response, GZIP compression, caching...
- Server capacity: concurrent users
- Stress to identify weak components...
Types of Usability Testing
- Do visitors understand the content? What do they read, remember?
- Is the navigation obvious?
- Is it easy to use?
- Accessibility tests (for people using assistive technology — WAI initiative at W3C)
Types of Semantic Testing
Semantic testing aims at identifying the underlying causes that trigger a good or bad user experience:
- The screen components, position and function
- What triggers their presence or appearance?
- What is the user looking for in a given situation?
- Is this expectation satisfied?
- Does the user understand the meaning of each component representation?
Testing is an important task. Conduct proper testing takes time. First, we have to define a set of testing tasks; we must ask the right questions; decide the priority; and finally set up the an appropriate suite of test tools
As for coding, early testing lowers the final set of tests to conduct. Example: testing the display of a page in various browsers, browser versions, platforms, is time-consuming. Testing the components of a page (reused in multiple pages) before final implementation saves time and efforts. Styles, scripts, visual elements are as many components to test. Security analysis and test from the start of coding significantly reduces further testing. These methods ease the final implementation.
The way we work
Conducting most of the debugging, performance, usability and semantic testing during the coding helps reduce end-of-project's testing. Early content, usability and semantic tests using a prototype brings useful data for the development. We dedicate 10 to 30% of our development time to the final testing and correcting defects and shortages detected.Pricing
Proper questioning to speed up final testing
- Coding components to test?
- Usability elements to test?
- Semantic components to test?
- Visual components to test?
- Number of templates or pages to test?
- Number of stylesheets involved?
- Number of scripts involved?
- Methods and tools or services to use for each test?
- Time needed for testing?
- Time needed for adjusting from tests results?