QA on Drupal projects - Drupal Dev Days Seville 2017

QA on Drupal projects

Alejandro Gómez - @agomezmoron#DrupalDevDays 2017

About me

#DrupalDevDays / @drupaldevdays @agomezmoron

agomezmoron.info.yml

name: Alejandro Gómezdescription: “QA & Tech lover”package: #DrupalDevDaysworks_on:- company: { name: @ladrupalera by @emergya, role: QA & Team lead }- company: { name: @EPSUPO, role: QA teacher }

type: Non-stop learnercore: DDD.2017

community: @SevillaQA organizer

Roadmap● What QA really means

● Dev & QA Teams: THE TEAM

● QA assembly instructions

● QA & Git-Flow

● Conclusions





● QA & Git-Flow

● Conclusions


What QA really means


Different approaches



First approach



Usual approach

Certifications

● Process.

● Defects.

● Validation.

● Continuous Integration



“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




● QA & Git-Flow

● Conclusions


@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.



The scrum process



The scrum process

Definition of Ready(DoR)

Definition of Done(DoD)



In short




● QA & Git-Flow

● Conclusions



QA assembly instructions

DRUPALKEA



What do we want to avoid?

DRUPALKEA



- 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.



Unit Testing

Functional testing

Responsive Testing

Performance testing




● QA & Git-Flow

● Conclusions



QA & Git-Flow

qa ci

US X

master

PR

CI validation & merge


QA & Git-Flow

qa cimaster

PR(on demand)CI validation

& merge

PR(realising)

tagCI validation

& merge


QA & Git-Flow

qa cimaster

PR(on demand)CI validation

& merge

PR(realising)

tagCI validation

& merge


QA & Git-Flow

pull request

Code Inspection

Delivery

Testing

accept/reject

Code Style


QA & Git-Flow

pull request

Delivery

Testing

accept/reject

Code Style


QA & Git-Flow

pull request

Testing

accept/reject

Code Style


QA & Git-Flow

pull request

accept/reject

Code Style






● QA & Git-Flow

● Conclusions



Conclusions


Conclusions

All you have seen needs a big effort:

Are you ready to do it?

Conclusions


Are you ready?


“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

Thanks to...


Thanks to...


Thanks to...


Thanks!


Technology

QA on Drupal projects - Drupal Dev Days Seville 2017