軟體系統測試簡介

38
蘇維宗, PMP 資訊工程學系 真理大學 1

Transcript of 軟體系統測試簡介

  • , PMP

    1

  • 9/7/2016 V1.0 105

    2

  • How to Develop Project Documents

    Guru99 Software Testing

    Glenford J. MyersThe Art of Software Testing

    3

  • 4

  • 5

  • ?

    6

    1994264(: http://tw.gigacircle.com/1095392-1)

    19998000

    (: http://www.visionlearning.com/blog/2012/09/21/tragedies-in-science-the-crash-of-the-mars-climate-orbiter/)

  • (Exhaustive Testing)

    (Pareto Principle)

    (Pesticide Paradox)

    7

  • (: )

    8

  • ()

    9

  • (Programmer) (Tester)

    10

  • LO-001

    () LO-003 1,0007

    11

  • (Requirements)

    (Design)

    (Code)

    (Test)

    (Maintenance)

    ?

    12

    0

    10

    20

    30

    40

    50

    60

    100

    Requirements Design Code System Test Maintenance

    Phase Error Found & Fixed

    Cost

    to F

    ix

    $1$5

    $20

    $50

    $100+

  • CMMI(Verification)

    The purpose of Verification is to assure that selected work products meet their specified requirements

    (Validation) The product or product components are validated to ensure that

    they are suitable for use in their intended operating environment.

    13

  • Service

    14

  • Banking System (BS 1.0)Login (LO 1.1)

    Balance (BA 1.2)

    Deposit (DE 1.3)

    Withdraw (WI 1.4)

    Transfer (TR 1.5)

    15

    Login

    Balance

    Deposit Withdraw Transfer

  • Interface

    Local data structures

    Boundary condition

    Independent paths

    Error handling paths

    JUnitCUnit

    16

    Balance

    Method 1

    Method 2

    Method 3

  • Big-Bang

    Incremental testing

    Top-down

    Bottom-up

    Sandwich

    17

  • Big-Bang

    18

    Test BS 1.0

    Test LO 1.1

    Test BA 1.2

    Test DE 1.3

    Test WI 1.4

    Test TR 1.5

  • Incremental()

    19

    Login

    Balance

    Incremental Testing 1

    Login

    Balance

    Deposi

    Incremental Testing 2

    Login

    Balance

    Deposit Withdraw

    Incremental Testing 3

    Login

    Balance

    Deposit Withdraw Transfer

    Incremental Testing 4

  • Incremental()

    20

    Login

    Balance

    (Stub)

    Deposit Withdraw Transfer

    Top-Down Integration

    Login

    (Driver)

    Balance

    Deposit Withdraw Transfer

    Bottom-Up Integration

  • Alpha testing

    Beta testing

    21

    Developer Site User Site

    Software

    Developer Site User Site

    Software

  • 22

  • (Revision History)

    (Scope of Testing)

    (Acceptance Criteria)

    (Testing Environment)

    (Testing Schedule, Procedure, and Responsibility)

    (Test Cases)

    (Test Result and Analysis)

    (Traceability Matrix)

    23

  • 24

    2010/10/31 0.1 Draft

    2010/12/7 1.0 Release

  • (Banking System)(Integration Testing)(Acceptance Testing)

    25

  • (CriticalImportantDesirable)(: )

    26

  • 27

    Ethernet

    Ethernet

    BS 1.0Client

    Ethernet

    1 Gbps Switch

    Database

  • At least 2 GHz processor

    At least 1GB RAM

    At least 600MB of free disk space after OS has been installed

    Windows Server 2008 R2

    SQL Server 2012

    At least 1 GHz processor

    At least 1 GB of RAM

    ChromeFirefoxIE

    28

  • 100121016

    (100/5/1 ~ 101/5/11)

    (100/5/14 ~ 100/5/25)

    (101/5/28 ~ 101/5/31)

    (101/5/11)

    (100/5/31)

    (101/5/31)

    29

  • Incremental()

    30

    Login

    Balance

    Incremental Testing 1

    Login

    Balance

    Deposi

    Incremental Testing 2

    Login

    Balance

    Deposit Withdraw

    Incremental Testing 3

    Login

    Balance

    Deposit Withdraw Transfer

    Incremental Testing 4

  • 31

    Testing Cases Personnel

    FT1 ()

    FT2 ()

    FT3 ()

    PT1 ()

    PT2 ()

  • ()

    32

    Identification

    Name

    Requirement number

    Severity

    Test data

    Preconditions

    Steps

    Expected result

    Post Conditions

  • (/)

    (/)

    33

    FT1

    FT2

    PT1

    1,000

    7

  • 34

    Identification FT1

    Name

    Requirement number LO-001, BA-001

    Severity Critical

    Test data1. : user1, : pass1, : 1000

    2. : user2, : pass2, :500

    Preconditions

    Steps

    1.

    2. 11000

    3.

    4. 2500

    5.

    Expected result

    Post Conditions

  • 35

    Test Case Result (Pass / Fail) Comment

    FT1 Pass

    FT2 Fail

    FT3 Pass

    Rate 95%

    Test Case Expected Result Test Result Comment

    PT1 1,000 1,000

    PT2 10 seconds 3 ~ 12 seconds 80010

  • :

    36

    Test Cases

    RequirementFT1 FT2 FT3 PT1 PT2 PT3

    LO-001 V

    LO-002 V

    LO-003 V V

    BA-001 V

  • LO-001

    37

    Test Cases

    RequirementFT1 FT2 FT3 PT1 PT2 PT3

    LO-001 V

    LO-002 V

    LO-003 V V

    BA-001 V

  • 38