Software Testing Framework

  • Published on
    10-Apr-2015

  • View
    6.262

  • Download
    0

Embed Size (px)

DESCRIPTION

Software Testing Framework, For more information Check this site www.examsinfo.in

Transcript

<p>Software Testing FrameworkDocument version: 2.0</p> <p>Harinath V Pudipeddihari.nath@sqae.com http://www.sqae.com</p> <p>Table of ContentsTable of Contents ...........................................................................................2 Revision History .............................................................................................4 Testing Framework .........................................................................................5 1.0 INTRODUCTION ........................................................................................................................... 5 1.2 TRADITIONAL TESTING CYCLE ...........................................................................5 2.0 VERIFICATION AND VALIDATION TESTING STRATEGIES................................... 6 2.1 VERIFICATION STRATEGIES ..............................................................................6 2.1.1 REVIEW S ......................................................................................7 2.1.2 INSPECTIONS ..................................................................................8 2.1.3 WALKTHROUGHS ..............................................................................8 2.2 VALIDATION STRATEGIES ................................................................................8 3.0 TESTING TYPES ............................................................................................................................ 9 3.1 WHITE BOX TESTING .....................................................................................9 W HITE BOX TESTING TYPES................................................................................. 10 3.1.1 BASIS PATH TESTING ...................................................................... 10 3.1.2 FLOW GRAPH N OTATION ................................................................... 10 3.1.3 CYCLOMATIC COMPLEXITY ................................................................. 10 3.1.4 GRAPH MATRICES .......................................................................... 10 3.1.5 CONTROL STRUCTURE TESTING ........................................................... 10 3.1.5.1 Condition Testing ........................................................... 10 3.1.5.2 Data Flow Testing .......................................................... 10 3.1.6 LOOP TESTING ........................................................................................ 11 3.1.6.1 Simple Loops .......................................................................... 11 3.1.6.2 Nested Loops .......................................................................... 11 3.1.6.3 Concatenated Loops ................................................................. 11 3.1.6.4 Unstructured Loops .................................................................. 11 3.2 BLACK BOX TESTING ................................................................................... 11 BLACK BOX TESTING TYPES ................................................................................. 11 3.2.1 GRAPH BASED TESTING METHODS ....................................................... 11 3.2.2 EQUIVALENCE PARTITIONING .............................................................. 11 3.2.3 BOUNDARY VALUE ANALYSIS .............................................................. 12 3.2.4 COMPARISON TESTING ..................................................................... 12 3.2.5 ORTHOGONAL ARRAY TESTING ............................................................ 12 3.3 SCENARIO BASED TESTING (SBT).......................................................... 12 3.4 EXPLORATORY TESTING ....................................................................... 13 4.0 STRUCTURAL SYSTEM TESTING TECHNIQUES ........................................................ 13 5.0 FUNCTIONAL SYSTEM TESTING TECHNIQUES......................................................... 13 4.0 TESTING PHASES ...................................................................................................................... 14 4.2 UNIT TESTING ........................................................................................... 15 4.3 INTEGRATION TESTING ................................................................................. 15 4.3.1 TOP- DOWN I NTEGRATION.................................................................. 15Software Testing Framework V2.0 2 of 25</p> <p>4.3.2 BOTTOM- UP I NTEGRATION ................................................................. 15 4.4 SMOKE TESTING......................................................................................... 16 4.5 SYSTEM TESTING ........................................................................................ 16 4.5.1. RECOVERY TESTING ....................................................................... 16 4.5.2. SECURITY TESTING ........................................................................ 16 4.5.3. STRESS TESTING .......................................................................... 16 4.5.4. PERFORMANCE TESTING .................................................................. 16 4.5.5. REGRESSION TESTING .................................................................... 17 4.6 ALPHA TESTING ......................................................................................... 17 4.7 USER ACCEPTANCE TESTING ........................................................................... 17 4.8 BETA TESTING ........................................................................................... 17 5.0 METRICS ......................................................................................................................................... 17</p> <p>6.0 TEST MODELS .............................................................................................................................. 19 6.1 THE V MODEL .......................................................................................... 19 6.2 THE W MODEL ......................................................................................... 20 6.3 THE BUTTERFLY MODEL ................................................................................ 21 7.0 DEFECT TRACKING PROCESS.............................................................................................. 23</p> <p>8.0 TEST PROCESS FOR A PROJECT ........................................................................................ 24</p> <p>9.0 DELIVERABLES ........................................................................................................................... 25</p> <p>Software Testing Framework V2.0</p> <p>3 of 25</p> <p>Revision HistoryVersion No. 1.0 2.0 Date August 6, 2003 December 15, 2003 Author Harinath Harinath Notes Initial Document Creation and Posting on web site. Renamed the document to Software Testing Framework V2.0 Modified the structure of the document. Added Testing Models section Added SBT, ET testing types.</p> <p>Next Version of this framework would include Test Estimation Procedures and More Metrics.</p> <p>Software Testing Framework V2.0</p> <p>4 of 25</p> <p>Testing FrameworkThrough experience t hey det erm ined, t hat t here should be 30 defect s per 1000 lines of code. I f t est ing does not uncover 30 defect s, a logical solut ion is t hat t he t est process was not effective.</p> <p>1.0 IntroductionTest ing plays an im port ant role in t odays Syst em Developm ent Life Cycle. During Testing, we follow a systematic procedure to uncover defects at various stages of the life cycle. This fram ework is aim ed at providing t he reader various Test Types, Test Phases, Test Models and Test Met rics and guide as t o how t o perform effect ive Test ing in t he project. All t he definit ions and st andards m ent ioned in t his fram ework are exist ing ones. I have not alt ered any definit ions, but where ever possible I t ried t o explain t hem in sim ple words. Also, t he fram ework, approach and suggest ions are m y experiences. My int ent ion of t his fram ework is t o help Test Engineers t o underst and t he concept s of t est ing, various t echniques and apply t hem effect ively in t heir daily work. This framework is not for publication or for monetary distribution. I f you have any queries, suggest ions for im provem ent s or any point s found m issing, kindly write back to me.</p> <p>1.2 Traditional Testing CycleLet us look at t he t radit ional Soft ware Developm ent life cycle. The figure below depicts the same. Requirements Requirements</p> <p>Design</p> <p>Design</p> <p>Te st</p> <p>Code</p> <p>Code</p> <p>Test</p> <p>Maintenance</p> <p>Maintenance Fig A Fig B</p> <p>I n t he above diagram ( Fig A) , t he Test ing phase com es aft er t he Coding is com plet e and before the product is launched and goes into maintenance.</p> <p>Software Testing Framework V2.0</p> <p>5 of 25</p> <p>But , t he recom m ended t est process involves t est ing in every phase of t he life cycle ( Fig B) . During t he requirem ent phase, t he em phasis is upon validat ion t o det erm ine t hat t he defined requirem ent s m eet t he needs of t he proj ect . During t he design and program phases, t he em phasis is on verificat ion t o ensure t hat t he design and program s accom plish t he defined requirem ent s. During t he t est and inst allat ion phases, t he em phasis is on inspect ion t o det erm ine t hat t he im plem ent ed syst em meets the system specification. The chart below describes the Life Cycle verification activities. Life Cycle Phase Requirements Verification Activities Determine verification approach. Determine adequacy of requirements. Generate functional test data. Determine consistency of design with requirements. Determine adequacy of design. Generate structural and functional test data. Determine consistency with design Determine adequacy of implementation Generat e st ruct ural and funct ional t est dat a for programs. Test application system. Place tested system into production. Modify and retest.</p> <p>Design</p> <p>Program (Build)</p> <p>Test Installation Maintenance</p> <p>Throughout the entire lifecycle, neither development nor verification is a straight- line act ivit y. Modificat ions or correct ions t o a st ruct ure at one phase will require modifications or re- verification of structures produced during previous phases.</p> <p>2.0 Verification and Validation Testing Strategies2.1 Verification StrategiesThe Verificat ion St rat egies, persons / t eam s involved in t he t est ing, and t he deliverable of that phase of testing is briefed below: Verification Strategy Requirements Reviews Performed By Users, Developers, Test Engineers. Explanation Requirement Reviews help in base lining desired requirements to build a system. Design Reviews help in validating if the design meets the requirements and build an effective system. Code Walkthroughs help in analyzing the coding techniques and if the code is meeting the coding standards Deliverable Reviewed and approved statement of requirements. System Design Document, Hardware Design Document.</p> <p>Design Reviews</p> <p>Designers, Test Engineers</p> <p>Code Walkthroughs</p> <p>Developers, Subject Specialists, Test Engineers.</p> <p>Software ready for initial testing by the developer.</p> <p>Software Testing Framework V2.0</p> <p>6 of 25</p> <p>Code Inspections</p> <p>Developers, Subject Specialists, Test Engineers.</p> <p>Formal analysis of the program source code to find defects as defined by meeting system design specification.</p> <p>Software ready for testing by the testing team.</p> <p>2.1.1 Reviews The focus of Review is on a work product ( e.g. Requirem ent s docum ent , Code et c.) . Aft er t he work product is developed, t he Proj ect Leader calls for a Review. The work product is dist ribut ed t o t he personnel who involves in t he review. The m ain audience for t he review should be t he Proj ect Manager, Proj ect Leader and t he Producer of the work product. Major reviews include the following: 1. In Process Reviews 2. Decision Point or Phase End Reviews 3. Post Implementation Reviews Let us discuss in brief about t he above m ent ioned reviews. As per st at ist ics Reviews uncover over 65% of t he defect s and t est ing uncovers around 30% . So, it s very important to maintain reviews as part of the V&amp;V strategies. In- Process Review In- Process Review looks at t he product during a specific t im e period of a life cycle, such as act ivit y. They are usually lim it ed t o a segm ent of a proj ect , wit h t he goal of ident ifying defect s as work progresses, rat her t han at t he close of a phase or even later, when they are more costly to correct. Decision- Point or Phase- End Review This review looks at t he product for t he m ain purpose of det erm ining whet her t o cont inue wit h planned act ivit ies. They are held at t he end of each phase, in a sem iform al or form al way. Defect s found are t racked t hrough resolut ion, usually by way of t he exist ing defect t racking syst em . The com m on phase- end reviews are Software Requirements Review, Critical Design Review and Test Readiness Review.</p> <p>The Soft w a r e Re qu ir e m e n t s Re vie w is aim ed at validat ing and approving t he docum ent ed soft ware requirem ent s for t he purpose of est ablishing a baseline and ident ifying analysis packages. The Developm ent Plan, Soft ware Test Plan, Configurat ion Managem ent Plan are some of the documents reviews during this phase. The Cr it ica l D e sign Re vie w baselines t he det ailed design specificat ion. Test cases are reviewed and approved. The Te st Re a din e ss Re vie w is perform ed when t he appropriat e applicat ion com ponent s are near com plet ing. This review will det erm ine the readiness of the application for system and acceptance testing.</p> <p>Post Implementation Review These reviews are held aft er im plem ent at ion is com plet e t o audit t he process based on act ual result s. Post - I m plem ent at ion reviews are also known as Postmortems and are held t o assess t he success of t he overall process aft er release and ident ify any opport unit ies for process im provem ent . They can be held up t o t hree t o six m ont hs after implementation, and are conducted in a format.Software Testing Framework V2.0 7 of 25</p> <p>There are three general classes of reviews: 1. Informal or Peer Review 2. Semiformal or Walk- Through 3. Format or Inspections Pe e r Re vie w is generally a one- to- one m eet ing bet ween t he aut hor of a work product and a peer, init iat ed as a request for im port regarding a part icular art ifact or problem . There is no agenda, and result s are not form ally report ed. These reviews occur on an as needed basis throughout each phase of a project. 2.1.2 Inspections A knowledgeable individual called a m oderat or, who is not a m em ber of t he t eam or t he aut hor of t he product under review, facilit at es inspect ions. A recorder who records the defects found and actions assigned assists the moderator. The meeting is planned in advance and m at erial is dist ribut ed t o all t he...</p>

Recommended

View more >