Can you give examples of a Test Plan for a PR

I really like testing plans and generally follow a simple framework based on principles I’ve learned from others and insights I’ve heard from folks here at Taro.

I find that a testing plan should enable other engineers, even those with less context about your PR, to validate that it works as expected. This doesn’t necessarily mean you’re okay with an approval from someone without context. Regardless this is the principle:

If you can create a testing plan that lets a new team member with a fresh codebase validate your changes, it builds huge confidence for folks who are knowledgeable about the problem / feature.

So with that in mind, there’s no one-size-fits-all solution. However, following the principle mentioned above will guide you toward something like this:

-----
Testing Plan

Automated

1. Ensure docker is running
2. Run bash e2e.sh ... whatever your e2e, integration, or high value unit tests are
3. Make reference to the tests in the diff

Insert screen shots of passing -> also point to passing in the CICD pipeline

Manual

1. Ensure docker is running
2. $ bash startup.sh test
3. Navigate to localhost:3000/xxxx
4. Do X Y Z
5. "Expect this thing to look like this"
6. Attempt edge case: Insert "some edge case" and expect "plan product requirement outcome"

Include screen recording of manual steps or screenshots
-----

Hopefully this helps!