Slime
Upcoming SlideShare
Loading in...5
×
 

Slime

on

  • 1,820 views

A mnemonic for ordering software testing

A mnemonic for ordering software testing

Statistics

Views

Total Views
1,820
Views on SlideShare
1,791
Embed Views
29

Actions

Likes
0
Downloads
29
Comments
0

3 Embeds 29

http://adam.goucher.ca 26
http://192.168.10.100 2
http://www.scoop.it 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Slime Slime Presentation Transcript

  • SLIME TWST 2007 Adam Goucher [email_address]
    • Time is often the major constraint placed upon testers.
    • Risk is introduced any time the code is changed
    • The greater the change, the greater the risk
    • The greater the change, the greater the risk
    • of revealing an old problem
    • The greater the change, the greater the risk
    • of introducing a new problem
    • The greater the change, the greater the risk
    • of having to re-test
    • SLIME is an ordering of testing tasks
    • The more structural the fix, the earlier we test
    • The more structural the fix, the earlier we test
    • to avoid re-testing
    • Re-testing takes time
    • Time is constrained
    • SLIME is a mnemonic
    • S is for Security
    • S is for Security -
    • XSS
    • S is for Security -
    • SQL Injection
    • S is for Security -
    • cryptography libraries
    • S is for Security -
    • authentication
    • S is for Security -
    • authorization
    • S is for Security -
    • authorization
    • S is for Security -
    • configuration
    • S is for Security -
    • data storage
    • S is for Security -
    • privacy
    • L is for Languages
    • L is for Languages –
    • stored
    • L is for Languages –
    • retrieved
    • L is for Languages –
    • displayed
    • L is for Languages –
    • in english
    • L is for Languages –
    • en français
    • L is for Languages –
    • auf Deutsch
    • L is for Languages –
    • на русском языке
    • L is for Languages –
    • そして日本語で
    • I is for requIrements
    • I is for requIrements –
    • explicit
    • I is for requIrements –
    • what I expected
    • I is for requIrements –
    • what management expected
    • I is for requIrements –
    • what the customer expected
    • I is for requIrements –
    • what the customer wanted
    • I is for requIrements –
    • implicit
    • I is for requIrements –
    • adequate speed
    • I is for requIrements –
    • usable
    • I is for requIrements –
    • accessible
    • I is for requIrements –
    • convenient
    • M is for Measurement
    • M is for Measurement –
    • Load
    • M is for Measurement –
    • Stress
    • M is for Measurement –
    • Performance
    • M is for Measurement –
    • per minute
    • M is for Measurement –
    • per hour
    • M is for Measurement –
    • per day
    • M is for Measurement –
    • per week
    • M is for Measurement –
    • and is that okay?
    • E is for Existing
    • E is for Existing –
    • Does what worked last build still work?
    • E is for Existing –
    • Does what worked last week still work?
    • E is for Existing –
    • Does what worked last month still work?
    • E is for Existing –
    • Does what worked last release still work?
    • SLIME is a mnemonic
    • SLIME reduces schedule risk
  • Adam Goucher [email_address]
  • Spares
    • S ecurity
    • L anguages
    • requ I rements
    • M easurement
    • E xisting
    • L is for Languages –
    • i18n
    • L is for Languages –
    • l10n