-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QA process - what is it and where does it live? #32
Comments
|
Is this a good place for me to pop thoughts? |
@rjmk Yes please! |
Sorry, I was just on holiday so haven't had a time to jot anything down yet. I'll try and do so before next week |
Thanks @rjmk, hope you had a fantastic holiday! |
@jrans If you have some time before you head to pastures new (and whilst it's still What I'd ultimately like to get to is a checklist of things to look out for (QA 101 if you will!) but lessons learned would be amazing if you have time 🕐 🎉 |
My notes on QA life. I've found that a smooth QA process can make the whole project much more efficient and work more enjoyable. I strongly believe QA should be done at regular intervals and rules should be stuck to and kept strict. As soon as one member of the team doesn't abide it makes it much harder for everyone else and ultimately the project fails. You are working with each other not against each other and the progress of project is always key! These aren't hard set rules and every team is different and QA process should be adjusted to and agreed upon by everyone.
|
@iteles @nelsonic @Danwhy @SimonLab There you go finally! If you read over and see a typo, badly worded sentence, grammar then please do feel free to edit. I will proof read now (as I suggest) but has taken a while to write this. |
@jrans, this is AMAZING, thank you so much! |
@jrans wow! 😮 |
My thoughts on the QA process:
|
As the number of collaborators and dwyl open source modules grows, it stands to reason that the number of people reviewers for PRs will also grow.
There are certain processes in place for these reviews, which we need to capture and @rjmk can certainly add some 'lessons learned' to.
Seeing as these also affect contributors, should these processes live in the contributing repo?
The text was updated successfully, but these errors were encountered: