Dual running testing strategy (complete)

Open

Prerequesites

We would need to request RMT-F files from ESR to be able to ensure our new process has the required positions. We would also need the process to run for at least a day before comparing APP files to allow a comparable APP file to be produced e.g. any APP file after the first one produced.

Testing of this would be as follows:

• A diff of the APP and new APP file.

• A comparison of rejected messages and APC file errors

• Identifying any other discrepancies and understanding why this is happening.

This would need to be a manual check at first as any unknown others will need some interpretation. We would start by comparing all fields.

Success would be:

1. The new APP file contains all expected correct APP records.

2. The Rejected messages should contain all possible APC error records e.g. from poor formatting

3. The “Other discrepancies” should be understood and either resolved or accepted

Outstanding questions:

1. How do we have the systems both use the RMT file? Can initially be manually done for testing for the new process.

2. Where do we put the new app file so it is not consumed by ESR before we are ready for the changeover. AWS as they wont have access for the foreseeable future.

3. How do we efficiently read the Rejected messages. Manually to start, but neo solution in development.

Open