avoid 7 software testing project problems

8/14/2019 Avoid 7 Software Testing Project Problems

1/34

AutomatedQA Webinar

1


2/34

AutomatedQA Webinar

2


3/34

Today, the tips are not about technology.

We wont be covering TestCompletespecifically.

The focus is on people and communication.

3


4/34

What is a successful test project?

4


5/34

A successful test project starts with a clear,realistic set of objectives agreed on from the

top down. The project goals are communicated to all

project stakeholders. The project is completed on time with the

goals achieved as agreed.

5


6/34

Isnt that the goal of any smart project?

6


7/34

All projects should work that way but testprojects are often treated with less respect.

Its up to you to make the difference.

Resist the pressure to skip the basics ofproject preparation.

7


8/34

Your organization doesnt know why itstesting.

8

Image courtesy of db*photography


9/34

Before you start your testing project, giveyour decision makers a brief summary that

outlines the expected benefits.

Focus on the benefit to the organization.

9


10/34

Benefit: Estimate savings in development andsupport costs

Example: Estimated cost to find and fix bugs found by QA

before release: $320/bug Estimated cost to fix and support bugs found by

customers: $1,084/bug We expect to save more than $1,000 in development

and support costs for each bug found by QA and fixedbefore release.(Source: Critical Testing Processes by Rex Black, 2004)

10


11/34


12/34

Problem: Your organization doesnt knowwhy its testing.

How to avoid: Define the goals

Use simple metrics to illustrate benefits

Get buy in from decision makers Track the metrics

Follow up and share the results

12


13/34

Your organization hasnt agreed on what kindof problems youre looking for.

13

All tests are not equal

Image courtesy of Dave Bleasdale


14/34

Your organization hasnt agreed on what kindof problems youre looking for.

Test everything? Not possible. Business processes, business logic, UI standards,

performance, load tests, client configurations

Prioritize and communicate.

14


15/34

Create another one page summary thatoutlines what you can test and what you

cant. List categories like business logic,

installation/configuration and performancenot specific test details.

Share it with stake holders and decisionmakers and agree on it before starting.

15


16/34

Problem: Your organization hasnt agreed onwhat kind of problems youre looking for.

How to avoid: Dont agree to test everything.

Spell out up-front what will be tested.

Document what will not be tested. Get sign off from decision makers.

16


17/34

Raise your hand if someone on your team isbuilding a test framework right now

17

Image courtesy of jonny.hunter


18/34

Youre building test tools instead of doingtesting.

18

Image courtesy of gb500


19/34

Smart testers are also trying to improve theirtools and processes.

Encourage this.

But not at the expense of actual testing.

19


20/34

Problem: Youre building test tools instead ofdoing testing.

How to avoid: Put the tool work on hold.

Schedule time for tools.

Define a separate project. Require minimum # of new issues.

Do allow tool work later.

20


21/34

Youre testing the wrong things.

21

Image courtesy of kristin_a

These are easy to test,

but not important to test.


22/34

Testing priorities change

Exploratory testing is valuable but needsdirection.

Scripted testing is great but can turnredundant if unmonitored.

Use continuous feedback to stay on course.

22


23/34

Problem: Youre testing the wrong things. How to avoid:

Set priorities. Track whats been tested.

Track whats changed in builds.

Review reported issues vs priorities. Triage daily or at least weekly and adjust.

23


24/34

Your test team doesnt know how to test.

24

Image courtesy of Kristian D.


25/34

Your test team needs more training:

Testing basics

How to use the platform How to perform tasks

How to verify the business process/logic.

How to use the testing tools.

25


26/34


27/34

Development doesnt understand or cantreproduce your problem reports.

27

Image courtesy of Kaibara87


28/34

Development doesnt understand or cantreproduce your problem reports.

How to avoid: Report the problem first, not the solution. Include system configuration

Include the scripted test

Let the developer see the issue (screenshots, video)

Use VMs to reproduce

Embed testers in development

Pairs testing

28


29/34

Your tested system isnt testable enough.

29


30/34


31/34

Your tested system isnt testable enough. How to avoid, part 2:

Dev build server with automatic smoke test Use VMs for baseline configs

Embed developers in QA

Pairs testing

31


32/34

1. Your organization doesnt know why itstesting.

2. Your organization hasnt agreed on whatkind of problems its trying to find.

3. Youre building test tools instead of testing.4. Your team is testing the wrong things.

5. Your team doesnt know how to test.6. Development doesnt understand yourreports.

7. Your tested system isnt testable enough.

32


33/34

Questions about Test Project Problems?

If you have technical questions aboutTestComplete, please visitwww.automatedqa.com/support

33


34/34

avoid 7 software testing project problems

Documents