A simple presentation about how to build an efficient test organization in a large corporation

1. +
How to build an efficient
Test OrganizationTest organizations in large corporations

2. +
Introduction
 This presentation gives a simple overview of my proposal on
how to organize your testing in a large corporation in a very
simple manner

3. +
Organizational Overview Proposal
Development
Team a
Development Organization A
Development
TeamDevelopment
Team
Development Organization B
Development
Team aDevelopment
TeamDevelopment
Team
QA Organization
QA QA
Corporation

4. +
Testing in the Development Team
 As much testing as possible should be done within the
development team
 The development team can have dedicated testers, that may or
may not know how to code, or programmers could do the
testing
 The main test responsibility lies on the development team

5. +
Testers in the Development
Organization
 If different development teams are working together to build a
larger system, it may be necessary to have a small team of
testers that focus on system testing of the entire system
 Designing a modular system reduces the need for system
testing
 A large system test team is a symptom of an underlying
problem

6. +
Testers in the QA Organization
 If there are several development organizations there may be a need to
centralize some testing
 Testing which requires tools that are expensive or inefficient to have duplicated in
multiple organizations
 Example: IOT testing
 Competence which is expensive or inefficient to have duplicated in multiple
organizations
 Example: Localization testing
 But these are exceptions – very little testing should be done this far from the
development teams
 With only one development organization, this can be moved into that
organization

7. +
Regression Testing
 Everyone is responsible for running their own tests during
regression test activities
 This motivates programmers and testers to design the system
properly with testability in mind, and to automate efficiently
 During regression test activities you must always have a risk-
based approach
 You cannot run every test every time and still be efficient
 This drives the need to reduce system complexity and design the
system with this in mind

8. +
Levels of Testing
Development Team
Development Organization
QA Organization
Isolated Tests
Contract/Collaboration Tests
Integration Tests
System Tests
Equipment & Competence Specific
Tests
 I like to use the nomenclature
for all the tests done by the
development team from the
following presentation
 Integrated Tests are a Scam
 https://vimeo.com/80533536

9. +
Conclusion
 This is a simple and efficient way of organizing your testing in a
large corporation to drive good system design, quality
ownership, and a non-bloated test organization