Manual smoke test:
The background is we don’t want to give builds to QE that don’t install and dont do a simple happy path.    The ask is to ensure we do our diligence to give something that looks reasonable.  Ideally this will be handled automated with CI runs… until we get there we have asked Rayford to install the builds and do a migration with MTC to sanity test, then after that he tells QE they are good to consume.
 
 
I would like to ask us to do the same thing of have someone do a sanity check after the build and ensure QE can at least install and do a simple operation, in this case a Backup/Restore.

Follow https://docs.google.com/document/d/1kO22zp6wsRzNTAn9Aky_erbpVCm4LvTYzKW_PVp0t2c/edit for install
 

• Deploy the CPaaS built downstream build of OADP
• Run through basic backup and restore scenarios
  • Stateful Application Backup/Restore - MSSQL https://github.com/openshift/oadp-operator/blob/oadp-0.3.0/docs/examples/stateful.md
  • Stateless Application Backup/Restore - Nginx https://github.com/openshift/oadp-operator/blob/oadp-0.3.0/docs/examples/stateless.md