quality spy overview

24
Quality Spy Makes software testing fun again… https://sourceforge.net/projects/qualityspy/

Upload: andreaskleffel

Post on 21-May-2015

2.629 views

Category:

Technology


1 download

DESCRIPTION

When everybody would be a Quality Spy, bugs would fear of extinction.

TRANSCRIPT

Page 1: Quality Spy Overview

Quality Spy

Makes software testing fun again…

https://sourceforge.net/projects/qualityspy/

Page 2: Quality Spy Overview

Some theory first

Page 3: Quality Spy Overview

Developers know their enemy!

Page 4: Quality Spy Overview

But sometimes…

Page 5: Quality Spy Overview

What helps?

• Good development practices (constructive qa)• Good testing (analytical qa)

Quality Spy will improve your testing!

Even with best design practices software will contain errors. You can find them using Quality Spy. Nonethless good testing will never replace a solid design.

Page 6: Quality Spy Overview

Who should do testing?

• Real beta-users

• Professional testers

• Any developer should be a tester to some degree, too

Anyone should be a Quality Spy! Not only pro-testers.

Therefore tools should be productive and easy to use.

Anyone should be a Quality Spy! Not only pro-testers.

Therefore tools should be productive and easy to use.

Page 7: Quality Spy Overview

Quality Spy helps with…

• Defining a Test Strategy

• Plan-based Testing

• Exploratory Testing

• Lightweight Bugtracking

Page 8: Quality Spy Overview

Defining a Test Strategy

• Do I really need this? Yes!

• Think early about how to test!

• Think about test subject, testing reason, time frame, test location, method, equipment, testers, acceptance criteria

Page 9: Quality Spy Overview

Without a Strategy...

• … you search for bugs that don‘t matter and that is like:

Page 10: Quality Spy Overview

Plan-based Testing

• Create a test plan with test cases similiar to what developers do with unit tests– Prefer single assertion and small tests

• Execute that tests and see the results

This is perfect for verification. You need it at some point to know what works. But it‘s not perfect for findings bugs.

Page 11: Quality Spy Overview

Exploratory Testing

• Just start testing!

• Think of scenarios you want to test within the software

• Track what you are doing and finding

This is perfect for findings bugs and creating valuable feedback. It is not suited so well for verification. You don‘t see at a coverage-level what was tested.

Page 12: Quality Spy Overview

Lightweight Bugtracking

• Test one feature in one run and track all bugs in one „document“

• Developers should bulk-fix that defects at „once“

This is perfect for early feedback. It helps that bugs don‘t get piled up and that you spend too much time organizing and managing them.

Page 13: Quality Spy Overview

Now the program…

Page 14: Quality Spy Overview

Quality Spy UI

Page 15: Quality Spy Overview

Test Strategy

Page 16: Quality Spy Overview

Test Plan

Page 17: Quality Spy Overview

Test Runs

Page 18: Quality Spy Overview

Test Run Summary

Page 19: Quality Spy Overview

Execute the Test Plan

Page 20: Quality Spy Overview

Protocols

Page 21: Quality Spy Overview

Export to Mantis Bugtracker

Page 22: Quality Spy Overview

Summary

Page 23: Quality Spy Overview

Printable Reports

Page 24: Quality Spy Overview

https://sourceforge.net/projects/qualityspy/

Download at sourceforge:

Contact for help and discussions:[email protected]