Add release testing and acceptence testing steps to development workflow

medic / cht-docs

Documentation site for the Community Health Tookit

https://docs.communityhealthtoolkit.org

13 stars 18 forks source link

Add release testing and acceptence testing steps to development workflow #630

Open mrjones-plip opened 2 years ago

mrjones-plip commented 2 years ago

I was chatting with App Services about how our release and acceptance testing works. After reviewing our dev workflow page for code, I saw that these two topics are poorly represented.

We should foster confidence in how the product team does it's QA by publishing the steps we follow. I believe there's maybe some internal documentation we could use that doesn't need much refining to publish? This could either represent the process at a high level to amend to the Development Workflow page, or the entire process which then could be the document QA uses instead of the internal one.

mrjones-plip commented 2 years ago

cc:

@garethbowen - per our call earlier today - also to reference the #medic/cht-core/issues/6345 which QA totally caught!
@ngaruko - are you free to work on this ticket before your sabbatical?
@jonathanvq - FYI as follow up the task to reach out to App Serv. about this topic - we'll reach out to everyone instead ;)

ngaruko commented 2 years ago

@mrjones-plip I think so, I still have about 2 weeks. Will look at that early next week once 3.14 is out of the door.

ngaruko commented 2 years ago

@mrjones-plip Just added some notes to the documentation and got @garethbowen to review. He suggested we find ways to make results from performance testing public. QA will figure this out later, so leaving this ticket open for reference.

mrjones-plip commented 2 years ago

Nice work on this @ngaruko !