Draft testing section of playbook

[ewilson-adhoc]

Story

As an engineer responsible for maintaining a microservice, I would like guidance on special considerations for testing within this architecture, therefor I would like this data in the playbook.

Acceptance Criteria

• [x] Describe how to use Github actions for running tests.
• [ ] Use newman + Postman collections an example for how smoke tests can be run.
• [ ] Give code coverage guidelines (start at 75% as a baseline, more is better)
• [ ] Describe pact or contract testing -- we didn't do this, but maybe we should mention that it exists? (specifically, that this kind of testing is important for integrating different services).
• [ ] Give an overview of what testing is recommended for different stages of development (Unit testing, Functional testing, Integration/Systems tests).
• [ ] Guide for how to set up testrail for manual testing.
• [ ] Mention performance testing (possibly reach out to infrastructure for how-to)

Open Questions

Resources

This can serve as a base for this document: https://vfs.atlassian.net/wiki/spaces/IET/pages/2089189650/How+to+Deploy+Microservice+to+Development

We should also look at the documents that infrastructure has put out, to see if they have anything that is useful.

[ewilson-adhoc]

https://github.com/department-of-veterans-affairs/pst-iet-team.documentation/tree/migration_plan

[FHiatt]

separate section required for postman section