Testing a mixed collection after integration

The situation

They had a mixed collection that was not working as expected after integration. The existing method was not fully functional, but a new method would require significant changes. They needed to decide how to test the collection after integration. The collection was crucial for their work, and getting it right was important. They were considering different approaches to ensure the collection worked as expected.

What they weighed

• Use the existing method and prove it live

• Add a new route and prove only specific imports

What they decided

Run the existing disposable proof after integration

Why

The existing method already passed some checks, and the new integration fixed a key issue without requiring a new route. This approach preserved all types and order, making it the most straightforward solution. They wanted to avoid duplicating work and ensure the collection worked for all types, not just specific ones.

The first step

Wait for integration deployment, then rerun the test script and record the results

How they would know it worked

A successful test returns the expected results, with the correct order and no errors, and then returns an error after revocation

How it turned out

Not known yet. The result is added here when it comes in.