Document Unit/Integration testing strategy

ProvidenceGeeks / website-docs

Top level README and documentation space for development of the Providence Geeks website

https://www.pvdgeeks.org

4 stars 2 forks source link

Document Unit/Integration testing strategy #25

Closed saimatsumoto closed 6 years ago

saimatsumoto commented 6 years ago

Testing Guide wiki page

Type of Change

[x] New Documentation
[ ] Other (please clarify below)

Summary

[x] Establish philosophy and strategy
[x] Scope of the test
[x] Tool(s) used
[ ] Test cases / Acceptance Criteria

saimatsumoto commented 6 years ago

@thescientist13 @ekrasner1 @kpisano Please let me know if see anything else to be added.

thescientist13 commented 6 years ago

Looks like a good start to me @saimatsumoto !

saimatsumoto commented 6 years ago

@thescientist13 Will you please review?

What is the best way to document test cases/A.C. for Unit/Integration on this wiki page? (Does "Expectation" cover it at high level? is that sufficient?)
What is the tool we use for integration, jest as well?

thescientist13 commented 6 years ago

What is the best way to document test cases/A.C. for Unit/Integration on this wiki page? (Does "Expectation" cover it at high level? is that sufficient?)

I think what you have is good!

What is the tool we use for integration, jest as well?

Jest only applies to JavaScript projects, so that would only include website-frontend and **website-lambda-*** projects. On the backend for Java projects, JUnit is being used.