Lessons Learned in Software Quality 1

Post on 29-Jan-2015

106 views 3 download

Tags:

description

This is the presentation used during the session "Lessons Learned in Software Quality 1" conducted in Amman, PSUT (15, Dec, 2010). Presented by Belal Raslan (Director at Quality Partners) & Rayya Abu Ghosh (Quality Manager at Yahoo! Middle east).

Transcript of Lessons Learned in Software Quality 1

Lessons Learnedin Software Quality

Rayya Abu GhoshBelal Raslan

Am I QA or QC ?

Lesson 1

Am I QA or QC ?QA QCRelated to the auditing and improvement for the process used to develop the software.

Related to the verification of the project deliverables against the agreed upon requirements.

Deals with the process used to produce the product and not the product itself. Cares for the product itself.

Assigned to the process (i.e. QA is usually not a project member, exactly like the HR team)

Assigned to the project (i.e. QC is a project team member)

Deals with things related to :Process engineering, CMMi, ISO, TQM, Six sigma

Deals with things related to :Testing, Requirements Verifications, Design Verification, User Acceptance

QA is usually a senior position. QC can be entry level career.

QA can insure and improve quality QC can’t improve quality, it only exposes lack of quality

Lesson 1

How ? What?

Am I QC or Tester?

Lesson 2

QC Tester

Am I QC or Tester?QC TesterVerifies all the major project deliverables and not only the builds Verifies the build only (testing)

The efforts are usually focused to verify the deliverables of the early stages of the project and before coding.

The efforts are focused on Testing only.

QC includes testing. Testing is part of the QC activities.

Lesson 2

QE

QC

Testing

What makes a good test engineer?Lesson 3

Curious

Detail oriented

Communicator

Analytical

Flexible

isiveDeci

What makes a good test engineer?Lesson 3

Types vs. Levels of Testing

Lesson 4

Types vs. Levels of Testing

Lesson 4

Testing Type Testing Level• Functional• Performance• Usability• Security• Compatibility• Flexibility• ReusabilityAnd much more ..

• Unit or White box testing• Smoke testing• System Testing• Integration Testing• Acceptance Testing

-Levels usually related to time and include many types

Defining the scope of test

Lesson 5

• What can be tested?• What will be tested?• Who will test it?• Make it clear and sign off

FunctionalityIntegration

Security

Performance

Compatibility

Usability

Globalization /i18n

Bugs detection vs. prevention

Lesson 6

Bugs detection vs. prevention

Lesson 6

Trying to improve quality by testing is like trying to lose weight by stepping on the weight scale.

Bugs detection vs. prevention

Lesson 6

Quality efforts should be focused on the verification of the early deliverables and not just the code (i.e. Testing).

Smoke test first, it’s cheaper

Lesson 7

Do smoke test first, it’s cheaper!

Its more cost-effective to start with a fast smoke check for the build before applying the whole test case.

Fixing major bugs first may reduce the total number of bugs to be found.

Developers may try to gain more time by delivering incomplete builds.

Lesson 7

Write a bug that will be fixed

Lesson 8

Write a bug that will be fixed

Lesson 8

K.I.S.S. (Keep It Short & Simple)

Please, be polite

It should be impersonal (use 3rd person)

Remember, your goal is to get it fixed

Write a bug that will be fixed

Lesson 8

The DO NOTs :

“Dear Adam,…”, “Sincerely, Sara“

“I know ….”, “You know..”, “..waiting for your action, Dude”

Use of imperative language

Exclamation marks!!!

CAPS

Bug vs. Issue

Bug Priority vs. Severity

Lesson 9

Bug Priority vs. Severity

Lesson 9•The

importance of the bug from client or business perspective

Priority

•The importance of the bug from the system perspective

Severity

Never use bug tracking systems to measure performance

Lesson 10

Test time estimates!

Lesson 11

Test time estimates!

Lesson 11

There is no proven formula for test time estimate.

Things to be considered when estimating the testing time:

• Size of the requirements • Number of test cases• Coding time• Reusability• Learning curve (business, technology, test tools,..)• Testing time and budget• Testing scope (testing types to be performed)

You will not find all the bugs

Lesson 12

What documentation matters?

Lesson 13

What documentation matters?

Lesson 13

Requirements

Test Plan

Defect and issue reports

Test Summary reports

Sign off (release checklists)

Keen to know more

Lesson 15

Keen to know more

Lesson 14

• Trainings, sessions, open discussions• Online groups, forums, sites• Lean more about the business• Learn more about technology, tools• SDLC Processes (XP, agile, Iterative,

Waterfall…)• About users perspectives (usability)

Keep in touch

braslan@sq-partners.com rabughosh@yahoo.com

Belal Raslan rabughosh

@braslan @rayyaluna

Belal Raslan Rayya Abu Ghosh

Born to Teest!

Coming soon..session II