The document outlines Alejandro Gomez's presentation on QA for Drupal projects at DrupalDevDays 2017. It discusses different approaches to QA, emphasizing that QA and development teams should work as a single unit throughout the entire process. It also provides instructions for assembling a QA program, covering unit testing, functional testing, and other test types. Finally, it discusses how QA can integrate with Git and continuous integration workflows using pull requests and code reviews.
8. What QA really means
#DrupalDevDays / @drupaldevdays @agomezmoron
“Sometimes, you only have to sit and look at it from a different angle.”
- Commitment
- Continuous process
- Definition (DoR, DoD, workflow)
- Standards (code style, documentation, etc)
- Testing (to avoid defects)
- Delivering
- Validation (Have we done what we had to?)
QA RULES
9. Roadmap
● What QA really means
● Dev & QA Teams: THE TEAM
● QA assembly instructions
● QA & Git-Flow
● Conclusions
#DrupalDevDays / @drupaldevdays @agomezmoron
10. @agomezmoron#DrupalDevDays 2017
Dev & QA teams: THE TEAM
Some tips:
1. There is only a team.
2. The team is dedicated to excellence.
3. We share workflows.
17. @agomezmoron#DrupalDevDays 2017
QA assembly instructions
- Unit Tests guarantee the quality of some isolated pieces (ex: modules).
- Functional tests are split into different suites:
- Acceptance/Smoke: Guarantees the quality of the core of the project.
- Regression: Guarantees the quality of the entire app.
- Progression: Guarantees the quality of the current development (release).
- Performance tests guarantee the system availability.
- Responsive tests guarantee the defined responsive rules.
32. Are you ready?
#DrupalDevDays / @drupaldevdays @agomezmoron
“You take the blue pill, the story ends, you wake up in
your bed and you believe whatever you want to believe.
You take the red pill: you stay in wonderland and I will
show you how deep the rabbit hole goes.”
Morpheus, Matrix