Direct conversion risks operating outages
A London ambulance service abandoned its computer-aided dispatch replacement after implementation failed. With direct conversion, the old system has no live role when the new system is not ready, so the choice can create an operating outage.
Purpose, risks and tooling of change management explains why changes need controlled testing and monitoring. The first comparison identifies the testing level that should provide evidence before conversion begins.
Test levels and their environments
Environment names vary by organization. The test level is identified by scope, purpose, and the person making the decision.
| Attribute | Unit | Integration | System | Acceptance |
|---|---|---|---|---|
| Meaning | Tests one software component in isolation | Tests data flow and behavior between connected components or systems | Tests the complete integrated solution against its stated requirements | Tests whether the customer or business users accept the complete solution against agreed acceptance criteria |
| Usual environment | Development environment with isolated code and test doubles such as stubs or mocks | Controlled integration or test environment with connected components and test data | System test or staging environment that resembles production | User acceptance testing environment, normally staging or another controlled production-like environment |
| Scope | One function, class, module, or service | Interfaces, messages, APIs, databases, or connected services | End-to-end application and supporting components | Complete business workflow and user outcome |
| Main question | Does this component work by itself? | Do the connected parts exchange and process information correctly? | Does the complete solution meet its specified requirements? | Can the customer or business owner approve this solution for use? |
| Typical performer | Developer or component test team | Integration test team or developers working across components | Independent test team or system test team | Customer, business owner, or representative users |
| Evidence or result | Component test results and defect records | Interface results, message checks, and integration defects | Requirements-based system test results | Acceptance results, user feedback, and approval or rejection |
| Clue words in a scenario | one module, isolated function, developer, stub, mock, component | interface, API, message, two services, data exchange, connected systems | entire application, end to end, complete solution, system requirements | business users, customer, user acceptance, sign-off, acceptance criteria |
The first table connects each test name to its environment, scope, and decision maker.
Change documentation and patching provides the component inventory, baseline configuration, change request, and rollback information. These records identify what is being tested.
| Attribute | Direct | Parallel | Pilot |
|---|---|---|---|
| Operation | Turn off the old system and switch all users or sites to the new system at one planned time | Run the old and new systems at the same time for the same operation, then compare or reconcile results | Move a limited site, department, product, or user group to the new system before wider rollout |
| Old system | Unavailable after the switch unless restored | Continues to operate while the new system is checked | Continues for the sites or users outside the pilot; it may also run beside the new system at the pilot site |
| Live disruption risk | Highest because the whole operation changes at once | Lowest for continuity, although duplicate work and synchronization create cost and control risk | Limited to the pilot group, but problems can still affect that group |
| Rollback | Difficult and may require restoring the old system and converted data | Usually easiest because operations can return to the old system | Stop or reverse the pilot while the remaining operation stays on the old system |
| Best clue | everyone switches, old system is shut down, one cutover | both systems run, compare outputs, duplicate entry, keep the old system available | one branch, one warehouse, limited users, trial site before rollout |
| Important relationship | Direct is a method of timing the whole change | Parallel is a method of keeping both systems operating | A pilot can use either direct or parallel operation within the limited pilot group |
The second table changes the question from what is tested to how much of the live operation changes and whether the old system remains available.
Testing change and configuration controls later checks whether these environment and conversion controls were followed. Production is live and does not replace normal unit, integration, or system testing.
Testing and conversion classification rules
For testing, the separating axis is the question being answered. Scope moves from one component, to connected components, to the complete system, and finally to business acceptance.
Users watching a test does not make it acceptance testing. Acceptance requires a business or customer decision against acceptance criteria.
Loading diagram…
For conversion, ask how much of the operation changes at one time and whether the old system keeps running. Direct changes the whole operation at once. Parallel keeps both systems operating. Pilot limits the new system to a defined group.
Pilot and parallel can appear together. One branch may run both systems while the rest of the organization remains on the old system.
The table gives the attributes. The boundary gives the quickest classification rule. The practice cases change the scope or decision maker, then the final case changes rollout coverage.
Separating the four testing levels
Each scenario changes the scope or decision maker, not just the vocabulary. The deciding fact separates the correct test from its sibling tests.
Practice
A developer runs tests on one password-hashing function with mocked database calls before the function is connected to the application. Which type of testing is being performed?
A team connects the new order service to the inventory service and checks whether inventory messages are sent, received, and processed correctly. Which type of testing is being performed?
A test team runs the complete payroll application, database, access controls, and reporting process against the documented system requirements in a production-like environment. Which type of testing is being performed?
Store managers run the final order-to-cash workflows in a user acceptance environment and decide whether the system meets the agreed business acceptance criteria. Which type of testing is being performed?
After these classifications, the conversion approach changes when rollout coverage changes. Test environments and conversion approaches connects the testing level with the later conversion decision.
Changing rollout coverage changes conversion
Was: A company turns off its old order system at midnight and moves every warehouse to the new order system at the same time.
Which one? Identify the conversion approach from these facts.
Answer: The original approach was direct conversion. The whole operation changed at one planned time, and the old system was unavailable.
Now: The company changes the rollout so that only one warehouse uses the new order system first, while the other warehouses continue using the old system.
Which one now? Identify the conversion approach after the fact changes.
Answer: The new approach is pilot conversion. The changed fact is rollout coverage. The new system moved from all warehouses at once to one limited site first, while the old system remained for the other sites.
The old system being unavailable everywhere identifies direct conversion. The limited first site identifies pilot conversion. The takeaways keep these facts separate from the test-level distinctions.
Testing levels and conversion approaches
Unit testing: one component in isolation, usually in development.
Integration testing: connected components or systems exchanging and processing information.
System testing: the complete integrated solution checked against its requirements.
Acceptance testing: business or customer users decide whether the solution meets acceptance criteria.
Direct conversion: the whole operation switches to the new system at one planned time.
Parallel conversion: old and new systems operate together while results or operations are compared.
Pilot conversion: a limited site, group, or department uses the new system before wider rollout.
Testing axis: the scope and decision move from component correctness to business acceptance.
Conversion axis: the amount of the operation changed at once and whether the old system remains available.
Purpose, risks and tooling of change management explains why these facts control change risk. Testing change and configuration controls checks whether the selected environment and conversion controls were actually used.
Unlock the full lesson and continue reading
Signup to continue reading this lesson and unlimited access questions, flashcards, AI notes, and more

