Background

Fuzz testing should be used to create round trip testing and pick up issues in conversion.

Fuzz tests auto generate data to put into fields and we can ensure that combinations of fields are converted appropriately and also pick up when new fields are introduced into the APIs by fuzz testing and ensuring that fields are correctly round tripped.

We would like to set up a pattern for fuzz testing that can be used across various providers as we implement new provider conversions.

Steps

• Set up fuzz testing for AWS MAPI to CAPI conversion
• Factor the fuzz tests into utils that can easily be re-used
• Add TODOs where current conversions create fuzz exceptions
• Do the same for CAPI to MAPI

Stakeholders

• Cluster Infra

Definition of Done

• Fuzz testing is introduced to catch future breakages and help identify issues in round trip conversions.

• Docs

• <Add docs requirements for this card>

• Testing

• <Explain testing that will be added>