CHAPTER 10 Testing Introduction Testing implies matching a prescribed set of quantifiable criteria against performance to find errors.

Types of Testing Concept testing - trying out the main project ideas on selected groups of people representative of the intended user group. Prototyping - a mock up of several of the key features from the program. Peer review – get colleagues to bring their experience to bear on them. Usability tests – rigorous tests, usually applied when the project has been integrated and is ready for release. Field trials – the application is tested in situ with the users (observation + interview) Acceptance testing – relates more to the operation and functional performance of the code, and is derived from software development.

Developmental testing (‘alpha test’) and Acceptance testing (‘beta test’) Testing means examining the project performance according to the specifications that have been agreed. ( Testing = examining aspects of performance) It includes: i) the robustness of the code or compatibility of the website across different browsers. ii) the structure and content of the program or website. iii) the interface. iv) the interactivity v) the performance of the program or site under specific conditions vi) the look and feel and perhaps accessibility issues.

Developmental testing (‘alpha test’) Developmental testing means the numerous checks that are carried out during the course of development to ensure that each part of the project meets its specification. Another point that is self-evident once stated is that testing the program against specifications is a continuous process during development. A lot of evaluation occurs during project development. If it is a good team, they will monitor each other’s performance in a constructive way.

Acceptance testing (‘beta test’) Acceptance testing in multimedia is the closest to pure software testing because it addresses the code underlying integration. The test phase is cyclical: developmental refinement occurs to ensure each sign-off stage. The assembly of all the parts according to agreement leads up to integration of the pieces and acceptance testing. See Sample acceptance test report sheet pg. 256 The sheet may seem over-bureaucratic, and it should be adapted or discarded depending on the type of project at the discretion of the project manager and depending on the level of testing required by the client.

Testing Strategy Testing strategy means stating in writing what measures will be taken to ensure that the final program meets the client’s requirements. This will include: i) noting the number and type of sign-off stages, ii) the responsibilities of team members to meet the technical and functional requirements at each stage, iii) the analysis of the users if applicable, iv) a peer review process if applicable, v) the building and trialing of a prototype if necessary, vi) whatever other methods you decide to employ during the development stages.

Cont… Testing Strategy The developmental testing is part of the testing strategy. Stages of testing (refer to pg. 258) i) Project definition scope and proposal ii) Define testing strategy iii) Production – Developmental testing (sign-off) iv) Design adjustments ( sign-off) v) Final design adjustments ( sign-off) vi) Integration vii) Acceptance testing. Operational errors corrected ( final sign-off)

Summary Multimedia does not have a strong tradition of testing. Web developments is beginning to develop a clearer relationship with the methods of testing from other disciplines. There are many forms of testing. Each has its strengths and weaknesses in relation to the needs of an application. The project manager has to balance the needs of the application with time and cost factors to devise a testing strategy. The client has to agree to the strategy in the full knowledge of what it includes and what it excludes so there are no last-minute recriminations.

Summary Developmental testing is the combination of sign-offs of the completed parts of the project as well as the natural refinement of the individual assets during the development process. Acceptance testing takes place at the final stage of the project to predefined criteria specified in the testing strategy. The integrated code is tested, and the robustness of the project is scrutinized. Final sign-off agrees that the team has met its responsibilities and that the application performs as specified.