7.3 Development and Testing

2026 Syllabus Objectives

  • Testing: The need to test the system before implementation
  • Test designs, test strategies, test plan: Test data, expected outcomes, actual outcomes, remedial action following testing
  • Test designs including: The testing of data structures, file structures, input formats, output formats and validation routines
  • Test strategies including: To test each module, each function and the whole system
  • The definition, characteristics and use of test data: Using normal, abnormal and extreme data
  • The use of live data

The Need for Testing Before Implementation

https://cambridgeassistant.com

🔑 Why Testing is Critical

Before any system can be implemented and go live, it must undergo thorough testing to ensure it functions correctly. Testing is essential because:

  • Even though individual modules may work satisfactorily on their own, when they are all put together there may be data clashes, incompatibility issues, and memory problems
  • The system must be as perfect as possible before it goes live
  • Testing helps identify issues with input and output methods, file and database structures, and validation and verification methods
  • It is a very time-consuming process but necessary to ensure system reliability

Testing must be completed at multiple stages: individual modules, integrated modules, and the whole system functioning together.

Test Designs

https://cambridgeassistant.com

Test designs specify what aspects of the system need to be tested. According to the syllabus, test designs should include testing of:

📌 Components to Test

  1. Data structures - How data is organized and stored
  2. File structures - How files are organized and accessed
  3. Input formats - How data is entered into the system
  4. Output formats - How data is presented to users
  5. Validation routines - How the system checks data is valid and acceptable

Each of these components requires careful testing to ensure they function correctly both independently and when integrated with other system components.

Test Strategies

https://cambridgeassistant.com

Test strategies define the approach and sequence for testing the system. The syllabus identifies three key levels of testing:

🎯 Levels of Testing

1. Module Testing

  • Testing of each individual module needs to be done to ensure each one functions correctly on its own
  • Each module is tested independently before integration
  • Helps identify problems within specific components

2. Function Testing

  • Testing of each function within modules
  • Ensures specific features and capabilities work as intended

3. System Testing

  • Once the development of each module is completed, the whole system needs to be tested (i.e. all modules functioning together)
  • Even though each individual module may work satisfactorily, integration testing is essential
  • Tests for data clashes, incompatibility, memory issues, and other integration problems

If issues are discovered during system testing, it may lead to a need to improve the input and output methods, file and database structures, validation and verification methods. Then the system will need to be fully tested again.

Sign in to view full notes