Software Testing ConferenceManchester

QA Engineer: Nurul Miah

Google Testing PhilosophyGoogle is an engineering /

computer science centric company

Quality must be owned by engineering

Test must be part of

engineering

Value in fixing bugs not

finding them (potential)

Google Testing Philosophy20% Time Project Mobility Fail Fast

Google Test Automation

Results can be checked by a

machine

No human judgement or cleverness is

required

So important it can’t be left to chance Repetitive

C++

QA

Quality Assurance

Confidence

Why do we test?

To provide feedback on progress

To inform stakeholder decisions

To learn!

Acts as an enabler

An 80% solution today instead of 100% solution tomorrow.

Markets are moving too fast to provide 100% customer solutions.

Software Development

DEVELOPERS

Roles & Responsibilities

Best time to find bugs is in development Testing is everyone’s job Developers own quality for every piece of

code they touch Person writing the code is the person most

qualified to do the testing Minimise platform dependencies Python, C++, Java & JavaScript Involve testers throughout development All code should be structured.

RISKS

Playing around with Risks

Likelihood

Don’t focus on RESULTS

Impact

Focus on DECISIONS

Remove causes Create Med / Low risks

Successful people ask better questions!

“Someone who knows HOW will always have a job”

“Someone who knows WHY will always be his/her boss”

“WHY? Is more important than HOW? Or WHO?”

TECHNIQUES &

PROCESSES

Visualising Test Progress: Board

Test Coverage: Mind Map

Risk-Based Test Planning: ACC

A - Attributes

C - Components

C - Capabilities

“Fast” “Secure” “Stable” “Elegant”

“Search” “Database” “Cart” “Printing”

“Database is Secure” “Search is Fast”

Replace a conventional test plan

Fast to writeFramework for calculating risk

surface map

Direct you toward missing

coverage

10 Minute Test Plan

A test plan that doesn’t lead to test cases is a waste of time!

Avoid prose in favour of bulleted lists

Don’t bother selling

No fluff, not a high school paper (A+B=C)

Make it flow, one section leads to another

If it isn’t actionable, leave it out

The outcome should be test cases

CONCLUSION

Continuous...

... Gives you great results!

INVOLVEMENT

INTEGRATION

INTERACTION

GUIDANCE

5% Fail Fast Speed!

Tools & Techniques

Quality Assurance

Read Code

Everyone Tests

Value in Fixing Bugs

Teach others

Get Involved

Early

“First learn the rules, then play better than everyone else”

ALBERT

EINSTEIN

Final Message...

THANK YOU