Please enable JavaScript.

Coggle requires JavaScript to display documents.

Fundamentals of Testing - Coggle Diagram

- - - - evaluate work product
    - - reduce the level of risk of inadequate sw quality
    - - to make decision
    - - context of component/system being tested
      - test level
      - sw development lifecycle model
  - - - show failures caused by defects
    - - find, analyze, fix defects
  - - - test planning
      - test analyzing
      - test designing
      - implementing test
      - reporting test progress & results
      - evaluating the quality of a test object
  - - - execution of the system being tested
      - execution of the component being tested
    - - not execution of component or system being tested
    - - Requirements
      - User Stories
      - Source Code
      - Design
- - - - time pressure
      - human fallibility
      - inexperienced/insufficiently skilled project participants
      - miscommunication btw prj participants
      - complexity of code, design, architecture, underlying problem, used technology
      - system understanding
    - - defect in code
      - environmental conditions
    - - false positive:
        
        occur in the way test/defect in test data, test environment, testware,...
      - false negative
        
        no detect defect
        
        reported as defect but not actually defect
  - - - activities direct,
        control an organization with regard to quality
        
        Quality Assurance
        
        adherence to proper process -> gain confidence on achievement of levels of quality
        
        support proper testing with process
        
        Quality control
        
        test activities
        
        support to achieve levels of quality
  - - - earliest actions/conditions contributed to create defect
    - - can analyzed to identify root cause
- - - - budget & resource
      - timescale
      - complexity
      - contractual & regulatory requirement
  - - - test analysis
        
        purpose
        
        determine what to test with measurable coverage criteria
        
        identify testable feature
        
        define associated test condition
        
        activities
        
        analyze test basis appropriate to test level
        
        requirement specifications
        
        design & implementation info
        
        implementation of component & system
        
        risk analysis report
        
        evaluate test basis & test item to identify defect
        
        identify feature and sets of feature to be tested
        
        define & priority test condition for each feature
        
        capture bi-directional traceability btw elements of test basis & test condition
      - test planning
        
        define testing objective
        
        define approach to meet objective within constraint
      - test monitoring & control
        
        test monitoring
        
        comparison of actual progress with planned one using test monitoring metrics
        
        test control
        
        take action to meet objective
      - test design
        
        purpose:
        
        how to test
        
        activities
        
        design & priority test cases and set of test case
        
        identify test data -> support test condition and test case
        
        design test environment & identify required infrastructure & tool
        
        capture bi-directional traceability btw test basis, test condition, test case
      - test implemetation
        
        purpose:
        
        do we have everything in place to run the test?
        
        activity
        
        develop & prioritize test procedure, create automated test scripts
        
        create test suite from test procedure & automated test script
        
        arrange test suite within test execution schedule
        
        build test environment, verify set up correctly
        
        prepare test data & ensure it is loaded properly on test environment
        
        verify & update bi-directional traceability btw test basis, test condition, test case, test procedure, test suite
      - test execution
        
        test suite run with test execution schedule
        
        activities
        
        record ID & version of test item/test object/test tool/testware
        
        execute test manually or using test execution tool
        
        compare actual result with expected one
        
        analyze anomalies to establish cause
        
        report defect
        
        log outcome of test execution
        
        repeat test activity
        
        verify & update bi-directional traceability btw test basis, test condition, test case, test procedure, test result
      - test completion
        
        purpose
        
        collect data from completed test activity
        
        when to occur
        
        sw system is released
        
        test project is completed
        
        agile prj iteration is finished
        
        test level is completed
        
        maintenance release is completed
        
        activity
        
        check defect report is closed or not
        
        create test summary report to communicate
        
        finalize & archive test environment, test data, test infrastructure, testware for later reuse
        
        handover testware to maintenance team/other prj team/stakehoder
        
        analyze LLBP -> improve in the future
        
        use the info gathered to improve test process maturity
    - - is captured & managed using test management tool & defect management tool
      - test planning work product
        
        include test pan
        
        test basis info
      - test monitoring & control work product
        
        type of test report
        
        test progress report
        
        test summary report
        
        address prj management concerns
        
        task competion
        
        resource allocation
        
        resource usage
        
        resource effort
      - test analysis work product
        
        define & priority test condition
        
        result in the discovery & reporting of defects in test basis
      - test design work product
        
        results in test case -> exercise test conditions
        
        result in design/identification of necessary test data
        
        result in design of test environment
        
        identification of infrastructure & tool
      - test implementation work product
        
        test procedure & sequencing of them
        
        test suite
        
        test execution schedule
        
        create work product using/used by tool
        
        create & verify test data & test environment
      - test execution work product
        
        documentation of status of individual test cases or test procedures
        
        defect report
        
        documentation about which test item, test object, test tool, testware were involved in testing
      - test completion work product
        
        test summary report
        
        action item for improvement of subsequent prj or iterations
        
        change request or product backlog items
        
        finalize testware
    - - implement effective test monitoring & control
      - analyze the impact of change
      - make testing auditable
      - meet IT governance criteria
      - improve the understandability of test progress report & test summary report
      - stakeholder understand technical aspect of testing
      - provide info to assess product quality, process capability, prj progress against business goal
- - - - verify & validate product, find defect,..
      - curiosity
      - professional pessimism
      - a critical eye
      - attention to detal
      - a motivation for good & positive communication & relationship
    - - design & build product
      - some tester's mindsets
      - interested in designing & building solutions than what wrong with those solutions
      - confirmation bias-> difficult