Shakal Shukla

Who must have commitment to deliver a Quality Software to the Customer ?

What is Quality

Quality Deliverables within time ? Bug Free software ? Customer Satisfaction ? Quality Deliverables within budget ?

What is Error ?

What is an error? - Unexpected result – [Swapnil]

- Mistake – Unplanned human action that produces an incorrect result.

- Fault / Failure / Error / Issue / Bug

Why software have a bugs? Miscommunication or No communication

Software Complexity

Programming errors

Changing Requirements

Time pressures / Unrealistic schedule

Egos

Poor documentation

Developer approach

Requirement gathering / Study. Best practices / Coding standards. Proper commenting. Unit Testing. Creative User Interface. Basic validations. Systematic approach while fixing issues. Comments in issue log.

Other Factors..

Performance of application

Security of application

Memory leakages

Questions to QA..

QA are paid for breaking software or Developer ?

What QA should pursue ? Error Or Developer

Keywords..

QA pursue errors not people.

QA breaks software because QA cares.

Goal of QAStandard Goal ..

Find issues Find it ASAP Get it fix

Practical Goal ..

• No issues from customer within 2-3 hours after delivery/release.

Do’s for QA..

Proper understanding of requirement. Discussion with Leads & Developer. Test Plan Review & Approve plan from Lead Test Cases Review & Approve cases from Lead Test Environment Test cases execution – Testing

Do’s for QA

Result Analysis Issue Log Verification of Issues Regression testing Automation

Don'ts for QA Understanding functionality & then write

test cases. Positive testing & then Negative testing Give enough time to developer Suggestion to Developer on tech front. Unorganized or Adhoc approch

Understanding of Requirement Read thoroughly

Create points or notes / Summary

Use tools – Mind Maps

Read / Discuss / Explore

Test Cases What is a use of Test cases ? Test Pre-requisites Language used Priority Mapping of Expected result & Actual

result. Use Tools – Test Director Redundancy Sequence of test cases

Testing Approach

4 W – 1 H Concept What Who When Where How

UI – Functional – Integration/Impact +ve testing first & then –ve testing.

Other testing

Performance Load Stress Security Compatibility Mutation

Result Analysis..Before logging issue..

Confirm functionality. Confirm spellings Confirm User interface -

Alignment Confirm impact

Issue log Proper language

Polite words should be used ( like need to be …)

Proper summary Wrong functionality (Is this sentence is

meaningful ?) Set proper Severity & Priority Steps to reproduce Pre-requisites Maintain each & every issue for proper

track issue

Issue log Issue status Proper comments from developer High severity/priority issue is “Not an

issue” – poor understanding of functionality.

Maintain History of sever bugs Follow up of bugs Issue should not be orally logged. Issue count is not important.

Issue log Use tools References Screen shots

Properly maintained on locationLess sizeMentioning of screen shotHighlight issue in screen shot

Reduce duplicates

Important points

Peer Reviews Quality standards Ideal Process

Last word…

All though QA and developer both runs to achieve qualities, but the only problem is they do it by their own way.

Both should complement each other.