Quality Assurance - QA Stages, Formatting, Guidelines and Web Quality Assurance Handbook

[MaxHarrisonGit]

Description

This PR Includes QA Stages, Formatting, Guidelines and Web Quality Assurance Handbook for Quality Assurance.

• QA Stages are at what point and stage should the Project be Tested.
• Formatting is how should the tests, results, and bugs be formatted and created.
• Guidelines is what needs to be followed either for QA or for Devs building with QA in mind.
• Web Quality Assurance Handbook is to outline and mark the Quality we expect for a Website that is entering QA.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• [ x] New feature (non-breaking change which adds documentation)
• [ x] Breaking change (This is a significant change)

Checklist

• [x ] I have ensured that I have used relative links where appropriate.
• [ x] I have proofread my documentation.

[AlexCatch]

Overall this a great bit of content, I only disagree with one point which I commented on.

The only issues I could find with it are styling / spelling / punctuation and flow.

Can we just go over the PR and make sure we don't have capital letters in the middle of sentences & that the flow makes sense when reading it back.

I also believe there is an open PR from Jared which more closely integrates the Web Quality Assurance side so I'm not sure how we'd proceed with that.

Overall great bit of work - just needs some polishing & more discussion from the rest of the team 😄 👍

[dextermb]

Not a bad document overall. I've suggested some changes, so if you want you can implement them with a single button click. I've also reworded some sections.

[AlexCatch]

Gone over it once more with a few suggestions, just like Dex's you should be able to just accept the suggestions and it they will be automatically applied.

Could we have the file names have dashes in-lieu of no seperators in file names please? Would make it look a fair bit cleaner.

[ash123456789]

Nice work 👍

[dextermb]

It's also worth noting that our git workflow says that commits should be commands: updated -> update 👍

[AlexCatch]

@wheatleyjj What's the next steps here are this includes the web quality assurance guide that is currently open at #94 ?

[jaredkove]

@AlexCatch If this gets approved first then I presume this one goes in and my efforts are semi-wasted.

[dextermb]

@AlexCatch If this gets approved first then I presume this one goes in and my efforts are semi-wasted.

🌈 Nothing is a waste

[AlexCatch]

@MaxHarrisonGit As we've made fair amount of changes in #94 IMO the web quality assurance guide should be removed from this PR & when the PR @wheatleyjj made has been merged in links can be updated etc.

What do you think about this?

[MaxHarrisonGit]

@AlexCatch I am fine with this, will remove it now 😄

[dextermb]

Let's not forget about the QA book for too long

[DivineOmega]

I believe we should get this both PR (#95) and @wheatleyjj's related PR (#94) merged in shortly, and resolve any conflicts as necessary.

[DivineOmega]

As has been discussed with a few people, this PR does currently contain a QA process different to how we currently work. Now this is outside of @MaxHarrisonGit's fork, feel free to make PRs that amend this.