or
How I learned to stop worrying and love a workflow
Quality assurance
What it is
- Quality Assurance fulfills three main purposes
- Testing out the code to make sure that each story delivers what was promised.
- When a feature is pushed out, QA makes sure that feature works based on the requirements.
- Manage and runs tests.
- Bugs happen.
- We build a library of tests to mitigate them.
- Bugs happen, but we learn from our mistakes.
- Create a library of "users" and "cases" that can be run through.
- "As a _______, I should expect to be able to do ________."
What it isn't
- There is no such thing as a completely bug free system.
- QA is there to make sure that any problems that happen will not happen again.
- There are steps that will be run through to try and make sure bugs don't happen, but there is no such thing as a perfect system.
- If you find one, let me know.
What you can do to help
Code Commenting
- Comment your damn code!
- No seriously, tell me what it does.
- In detail.
- I can't stress this enough.
- For realz.
-
Treat me like a 5 year old.
-
ELI5: How does your code work?
- Use Javadocs
- Standards are awesome to follow.
- Can auto-create some documentation with things like PHPDoc.
Documentation
- Give me an overview of what it does.
- Is a wiki the best format (discuss)?
- What parameters does it take in?
- What does it give back?
- Gimme details!
- The more specific the better.
Follow coding standards
- Not all rules are made to be broken.
- We do what we do for a reason.
Bring it all under one roof
- Live and Milesplit need to start using our standards.
- This is going to take time.
- Drivefaze needs to incorporate unit tests.
- We need to start writing unit tests, period.
- Not to mention functional tests (Casper?)
- You're going to love this Eram...
- Our hotfix workflow is going to need some work.
- Maybe a different workflow for offshores?
Quality Assurance
By Kevin Baugh
