https://www.meetup.com/ThoughtWorks_Koeln/events/275248029/

Presentation by

• Jo Will

• Shalini Saini

Table of Contents

• What is quality

• (in)famous bugs

• building quality in

• • waterfall

  • agile

  • tester -> QA

  • practices

  • • test pyramid

    • TDD

    • pair programming

• cross-functional requirements

• diversity and inclusion

---

1996 - 2008

6 months of testing phase

what went wrong?

during testing phase

- ignored practical cases (manual intervention breaks the process)

- load test under actual demand

big bang launch

takeaway

- consider practical scenarios

- don't do big bang release

measurement system

one team metric

other team imperial

accidentally used wrong treatment mode

cause: race condition causes wrong type of radiation

quality of customer service can be as important as quality of product

---

silos

for waterfall, in production is really scary

the sooner you find the bugs, the easier they are to kill

testing in waterfall vs agile, is very different

whole team is responsible for testing

shift left

Practice: Test Pyramid

failing UI test => add unit test

Practice: TDD

2) only when you refactor your tests well

Practice: Pair Programming

---

(renamed from non-functional requirements)

*Anais Nin

8% are white Caucasian males

8% of people use internet explorer

"can we just not support IE?" is like saying "can we just not supportwhite Caucasian males?"

Do you think that following coding standards and using software  quality tools is important during development to ensure quality code at that stage?

Whats about testing in production ? With canary environments (amazon does this) . That means only a few people get the new features. There is no real anger if this does not work because the next test other people get the new features

it's all about fast feedback

Unfortunately I have had only few project where we had a QA in a team. So 2 questions: 1) What are good arguments to sell the position of having a dedicated QA in a team? 2) How can a team that doesn't have the luck to get a QA deal with this situation?

argument:

• it's a backup

• specialised knowledge (eg. exploratory testing)

• awareness (vs focus on functional requirements)

• keep reminding people

• ensures: from planning phase to think about quality

Is QA something like governance ?

No, it's not one person'sresponsibility

It's not about compliance