hello-my-name-is-software-testing-v2-pdf

HelloMy Name is

Software Testing

Thursday, October 18, 12

Who am I?

IT Development Manager @ TARAD Dot Com

Assistance Services & Operation Manager @ Sanook.com

QA Specialist @ Sanook.com

Tester @ Sanook.com

System Administrator @ POPidols.net

Freelance Programmer

Prathan DansakulcharoenkitScrum Master + CBO + ITIL Coach @ OpenDreamConsult Manager @ FedilityQAOutsource Project Manager @ TARAD Dot Com


UNLEARN


Software Quality


Quality Triangle


Quality Triangle

Requirements


Quality Triangle

SpecificationRequirements


Quality Triangle


Software


Quality Triangle


Software

Gap


Quality Triangle

Requirements

Software

Gap


Quality TriangleSoftware

Gap


Quality Triangle

Gap


Quality Triangle


Quality Triangle

Requirements


Quality Triangle

Requirements Specification


Quality Triangle


Software


Quality Triangle


Software

It’s an IDEAL!!!


Quality Triangle


Quality Triangle

In the real WORLDThursday, October 18, 12

Quality Triangle


Software

In the real WORLDThursday, October 18, 12

Quality Triangle


Software

In the real WORLD

Software



Quality Triangle


Software

In the real WORLD

Software


Software



Quality Triangle


Software

In the real WORLD

Software


Software


Requirements

Software

Specification


Quality Triangle


Software

In the real WORLD

Software


Software


Requirements

Software

Specification

Software



Software Testing


Where Do bug Come?


Where Do bug Come?Requirements definition



System design



System design

Implementation



System design

Implementation

Support systems



System design

Implementation

Support systems

Inadequate testing of Software



System design

Implementation

Support systems

Inadequate testing of Software

Evolution


Cost of Bug


Cost of BugTester use 10 minutes to record 1 bug



350 bugs is used 3,500 minutes = 58 hours




Developer use 3 minutes to feedback 1 bug






Tester use 3 minutes to change status of 1 bug








58 hrs + 17 hrs + 17 hrs = 92 hr








58 hrs + 17 hrs + 17 hrs = 92 hr

4 days


What do you think software testing is?


Some Facts of Testing


Some Facts of TestingALWAYS be a chance that software will have bugs



CANNOT prove software works by testing it




DOES NOT prove that software is bug-free





Testing after software has been created DOES NOT improve its quality






Cost of removing bugs rises DRAMATICALLY in the later phases of the software development process






Cost of removing bugs rises DRAMATICALLY in the later phases of the software development process

QUALITY depends on 3 factors; People, Process and Tool


Some Facts in NASA

as the 120-tons space shuttle sits surrounded by almost 4 million pounds of rocket fuel..

...the last three versions of the program -- each 420,000 lines long-had just one error each. The last 11 versions of this software had a total of 17 errors...

Source: http://www.fastcompany.com/magazine/06/writestuff.html


http://www.fastcompany.com/magazine/06/writestuff.html

http://www.fastcompany.com/magazine/06/writestuff.html

Some Facts in NASA


Some Goals of Testing


Some Goals of TestingDetermine a product MEET business expectation



MINIMIZE the risk of error occurs




IS NOT the process to verify software work correct





Testing must be to DEMONSTRATE that software does have bug





Testing must be to DEMONSTRATE that software does have bug

Tester must find bug as EARLY as possible and make sure that they are fixed


What are testing types you know?


Testing Types


Testing TypesUnit testing



Integration testing



Integration testing

System testing



Integration testing

System testingUser Acceptance testing



Integration testing


Regression testing



Integration testing


Regression testing

Performance testing



Integration testing


Regression testing

Performance testing

Security testing



Integration testing


Regression testing

Performance testing

Security testingUsability testing



Integration testing


Regression testing

Performance testing

Security testingUsability testing

Compatibility testing


Testing Types

A

B C

DE

F G


Testing Types

A

B C

DE

F G

Module


Testing Types

A

B C

DE

F G

Module

Integrate


Testing Types

A

B C

DE

F G

Module

Integrate

SystemThursday, October 18, 12

Testing Types


Test Case


Test Case

inputs to test system and verify with expected outputs


Test Case

inputs to test system and verify with expected outputs

Test Case = Test Rule + Test Data


Test Iterations


Test IterationsTest to Pass


Test IterationsTest to Pass

Test to FailThursday, October 18, 12

Who feel responsible for QUALITY in traditional development (Waterfell)?


SOMEONE



WHOLE TEAM



Whole Team Approach


Whole Team ApproachTeam commitment to quality



Team responsible for testing




Tester get support, training





Developers doing testing activities






Tester and developer pair






Tester and developer pair

Get the right person


Team Organization

xA

Tester

Dev

Traditional Organization


Team OrganizationAgile Organization

DomainExpert Dev

Tester


3Cs

Card

Conversation

Confirmation


Test INFECTED


Quality Improvement by found defect EARLY


Automate Testing in the RIGHT time


Don’t tell your team, WE DO AGILE


Process’n Clock


We don’t build the softwareWe make it work with

QUALITY


Quality in every phase, Not afterthought


Keep in touch

email: [email protected]

twitter: @zyracuze

facebook: zyracuze

blog: www.welovebug.com


mailto:[email protected]

mailto:[email protected]

http://www.welovebug.com

http://www.welovebug.com

Thanks You


hello-my-name-is-software-testing-v2-pdf

Documents

quality trianglethursday

quality trianglein

quality trianglegapthursday

real worldthursday

software testingthursday

software qualitythursday

project manager

opendream consult manager