Testing strategy

[siddharthkp]

Putting this here, so that we don't forget 😅

Let me start from the other end, what do we want from our testing strategy? The answer for me is iterate with confidence, everything else is a byproduct.

The situations in which I feel under confident touching code right now are:

1. I don't know if this design change is intentional.
2. I don't know what else will change/break (components composed of this component and the places it is used in the application)
3. Adding props of a component might break another component
4. Changing logic in complex components should not break another component
5. Changing/improving prop type definitions might break cause validation errors elsewhere (in other components or the application using them)

Approach:

1. Visual testing

   1.1 Visual changes in components should be called out and approved
   1.2 Resulting changes in sample PoC should be called out and approved

2. API testing

   2.1 All combinations of props need to be laid out for error catching.

Groundwork needed:

1. We need a space where components with their variations are laid out (automated hopefully), this will be the space for catching + approving visual changes. Real snapshot testing?

2. We need more sample applications built with cosmos to catch issues in usage, this will help us experiment with our components before it reaches the product teams.

[siddharthkp]

We have a good testing strategy in place for now ✨