A l p e r M e r m e r

QA WORKSHOP

Hands-on applications of testing techniques and

automation frameworks.

WORKSHOP CALENDAR

Week 1 - Testing in general, QA Culture

Week 2 - Web Automation with Ruby (Cucumber, Cabybara)

Week 3 - Test organisation and transformation process

Week 4 - Cucumber, Capybara advanced techniques (DB

accessing, service calls)

Week 5 - Advanced Cucumber (hooks , parallelisation)

Week 6 - Windows Desktop automation with Cucumber and

AutoIt

Week 7 - Mobile Automation with Cucumber and Calabash

Week 8 - Performance testing with Cucumber and Jmeter

2

WEEK 1

- Why are we doing these sessions ?

- Why is testing important ?

- Who are the guardians of quality in a project ?

- What are the important characteristics of a QA ?

- Future of QAs in the world

3

WEEK 3 - TEST ORGANIZATION AND TRANSFORMATION

TestHive Workshops Week 3

Test Organisation and Transformation

Alper MERMER

testhive@googlegroups.com

twitter: @test_hive

4

WEEK 3 - TEST ORGANIZATION AND TRANSFORMATION

What are the main problems in test organisation and what

are the solutions ?

5

WEEK 3 - TEST ORGANIZATION AND TRANSFORMATION

Problem: Too little number of testers for projects

Solution

- Attend estimation and planning cycles

- Give feedback to stakeholders often

- Timebox tests and prioritize them

- Respect your own schedule and don’t let people bend it

- Automate everything you can

- and of course ask for new people immediately, assess the

situation well and warn the management of the consequences

6

WEEK 3 - TEST ORGANIZATION AND TRANSFORMATION

Problem: Too little time for testing in iterations (or phases)

Solution

- Similar to the previous problem

- Attend estimation and planning cycles as the testing team

- Automate everything and do it early

- Set cut off times and make them known very early in the

project

- Time box things and prioritize

- Bug triage is vital

7

WEEK 3 - TEST ORGANIZATION AND TRANSFORMATION

Problem: Conflicting environments for testing

Solution

- Employ continuous delivery

- Make developers use different environments

- Keep environments in sync

- Clean your test data after your tests

- Have seperate environments for exploratory, automation and

performance

- Employ dynamic machine provisioning

8

WEEK 3 - TEST ORGANIZATION AND TRANSFORMATION

Problem: Automations are falling behind

Solution

- Keep them alive, and always set aside time for them

- Practice ATDD, write your acceptance tests before coding

begins

- Timebox your day between Exploratory and Automated

testing.

- If you can’t do ATDD then assign the first few days of

iterations to automation.

- Make automation an integral part of your iteration.

- Employ continuous delivery

9

WEEK 3 - TEST ORGANIZATION AND TRANSFORMATION

Problem: Automations are taking too long to run

Solution

- Parallelize tests

- Employ dynamic machine provisioning

- Build “Journey Tests” and acceptance test to run with every

commit, set regressions to run by a schedule and with

deployments to pre-production.

- Refactor your automation code.

10

WEEK 3 - TEST ORGANIZATION AND TRANSFORMATION

Problem: Not everybody knows about test automation

Solution

- Share your knowledge

- Learn yourself everyday

- Review tools and frameworks for the best fit in your

organisation

- Demonstrate the importance of automation every chance you

get.

11

WEEK 3 - TEST ORGANIZATION AND TRANSFORMATION

THANK YOU

Questions ???

12