strategies for testing this project

[jhamman]

This project is unique because the visuals being developed here are expected to be embedded on a third-party site. For this reason, I think it would be wise to develop a plan to insure site reliability and interface consistency. I bet @katamartin will have some good ideas for both of these so let's use this issue to develop a testing plan and track any developments needed.

[katamartin]

I talked about this a little bit with @freeman-lab and it sounds like tests for visual consistency would be most useful here.

I'm to look into this a bit more, but using Cypress for screenshot tests sounds like a promising option here.

[jhamman]

Thanks @katamartin - I think this is along the lines of what I was thinking.

In terms of site reliability, I think data management is probably our biggest concern. We need to be careful about how and where we store the input data to these figures. Perhaps some strong life cycle rules on a bucket on gcs will do. I can tell you that https://carbonplan-scratch.s3.us-west-2.amazonaws.com/grist/relative_fire_risk.zarr is likely to get scrubbed here soon (currently used in the risk figure).

[jhamman]

Following up here. A few proposals that I think will satisfy most of my concerns here:

1. Enable a GCS retention policy for the data layers used here. This will protect from accidental deletion down the road.
2. Disable "pushing to main" in this repository. This will add an extra step to future updates that will help avoid premature merges / temporary outages.
3. Finish [wip] setup image snapshot testing #8, which will help us validate future changes to the site.

Is there anything I'm missing here?

[jhamman]

Confirming that 1 and 2 above are done.