Slime

Slide 1: SLIME TWST 2007 Adam Goucher adam_goucher@hotmail.com

Slide 2: Time is often the major constraint placed upon testers.

Slide 3: Risk is introduced any time the code is changed

Slide 4: The greater the change, the greater the risk

Slide 5: The greater the change, the greater the risk of revealing an old problem

Slide 6: The greater the change, the greater the risk of introducing a new problem

Slide 7: The greater the change, the greater the risk of having to re-test

Slide 8: SLIME is an ordering of testing tasks

Slide 9: The more structural the fix, the earlier we test

Slide 10: The more structural the fix, the earlier we test to avoid re-testing

Slide 11: Re-testing takes time

Slide 12: Time is constrained

Slide 13: SLIME is a mnemonic

Slide 14: S is for Security

Slide 15: S is for Security - XSS

Slide 16: S is for Security - SQL Injection

Slide 17: S is for Security - cryptography libraries

Slide 18: S is for Security - authentication

Slide 19: S is for Security - authorization

Slide 20: S is for Security - authorization

Slide 21: S is for Security - configuration

Slide 22: S is for Security - data storage

Slide 23: S is for Security - privacy

Slide 24: L is for Languages

Slide 25: L is for Languages – stored

Slide 26: L is for Languages – retrieved

Slide 27: L is for Languages – displayed

Slide 28: L is for Languages – in english

Slide 29: L is for Languages – en français

Slide 30: L is for Languages – auf Deutsch

Slide 31: L is for Languages – на русском языке

Slide 32: L is for Languages – そして日本語で

Slide 33: I is for requIrements

Slide 34: I is for requIrements – explicit

Slide 35: I is for requIrements – what I expected

Slide 36: I is for requIrements – what management expected

Slide 37: I is for requIrements – what the customer expected

Slide 38: I is for requIrements – what the customer wanted

Slide 39: I is for requIrements – implicit

Slide 40: I is for requIrements – adequate speed

Slide 41: I is for requIrements – usable

Slide 42: I is for requIrements – accessible

Slide 43: I is for requIrements – convenient

Slide 44: M is for Measurement

Slide 45: M is for Measurement – Load

Slide 46: M is for Measurement – Stress

Slide 47: M is for Measurement – Performance

Slide 48: M is for Measurement – per minute

Slide 49: M is for Measurement – per hour

Slide 50: M is for Measurement – per day

Slide 51: M is for Measurement – per week

Slide 52: M is for Measurement – and is that okay?

Slide 53: E is for Existing

Slide 54: E is for Existing – Does what worked last build still work?

Slide 55: E is for Existing – Does what worked last week still work?

Slide 56: E is for Existing – Does what worked last month still work?

Slide 57: E is for Existing – Does what worked last release still work?

Slide 58: SLIME is a mnemonic

Slide 59: SLIME reduces schedule risk

Slide 60: Adam Goucher adam_goucher@hotmail.com

Slide 61: Spares

Slide 62: Security Languages requIrements Measurement Existing

Slide 63: L is for Languages – i18n

Slide 64: L is for Languages – l10n