|
 Test
|
 |
|
. |
|
On the web, all faults and errors become public! |
|
|
|
|
Especially in a web environment, where customer loyality and customer satisfaction are "life-or-death" criteria, testing plays a particular role: Once the web site has gone live, errors can become very embarrassing. But, apart from functionality, your customer also expects performance, stability, availability, usability. The testing of web sites requires a systematic approach with a mixture of conventional and new test methods. |
|

|
|
Test Support Center
(German) Support and advice in all matters of testing
|
|
|
|
Testing is necessary throughout the entire course of the project, so make sure to start early! |
|
|
|
|
Web projects often have to be completed within a period of only two to three months. For this reason, there is hardly any time to build up testing know-how in the project. It is all the more important to start planning, but above all also conducting tests during the early stages of the project. Test planning that takes account of risks will focus on the key quality aspects to be tested. |
|
|
|
|
How can you provide sufficient testing in spite of short times to market? |
|
|
|
|
- Take your prototypes to the customer early on; rely on teamwork
(developers & testers) during the definition of the requirements
- Limit requirements engineering to an absolute minimum
(use cases, GUI behavior)
- Use a test management system (link between requirements
and test cases)
- Start testing in the early phases of development and design test cases in a systematic manner
- Define priorities for key scenarios (use case testing, load tests for a few typical cases)
- Define test cases also for key quality aspects relevant in a web environment such as performance, security
etc.
- Make deliberate use of automated regression tests
|
|
|
|
|
|