Please enable JavaScript.

Coggle requires JavaScript to display documents.

SWT_General, Topic 5: Test management, Topic 3: Static Techiques, Topic 6:…

- - - - application & business domain
      - technology
      - testing
- - - - test log indentifier
      - description
      - activity & event entries
    - - give test team & test manager feedback on how the testing work
      - provide visibility about test result
      - measure status of testing, test coverage
      - gather data for us in estimating future test efforts
- - - - 6 steps
        
        1.1 Defining the review criteria
- - - - without actually executing the software artefact
      - performed before the type of formal review discussed
      - unrelated to dynamic properties
      - goal: find defects rather than failures
  - - - complexity
      - cyclomatic complexity
      - control flow
    - - control flow structure
      - data flow structure
      - data structure
- - - - managements of testware: test plan, specification, resilts
      - management of test process
      - incident management tools
      - traceability
  - - - provide info about quality of software
      - code is examined, NOT executed
      - objective measires
  - - - generate test inputs
        
        from a formal specification
        
        from code
    - - data manipulation
        
        selected from existing DB/files
        
        created according to some rules
        
        edited from other source
  - - - character-based
        
        capture keystrokes & screen responses
        
        simulate user interaction
        
        test script in programmable language
        
        Interface to software
        
        run tests by human
        
        data, test inputs, expected results: in test repositories
        
        often automate regression tesitng
    - - defect difference between: ACTUAL test result VS expected value
        
        masking & filtering
        
        screen. character, bitmaps
      - normally included in TEST RUNNING TOOLS
      - stand-alone comparison tools for files/DB
  - - - provide run-time info
        
        flag unassigned pointer/ pointer arithmetic faults
        
        allocation, use, de-allocation of resource (memory leaks,....)
    - - load generation
      - transaction measurement
      - reports based on logs, graphs: load VS response time
  - - - Automate repetitive tasks
        (E.x: regression testing)
      - support manual test activities
        (Ex: test planing, test design, test report, monitoring)
- - - - a way to do a proof-of-concept
      - on small scale
      - sufficient time
      - experiment with different way
    - - learn more about tool
      - see how tool fit with existing processes/ doc
        how need to change to work well
      - decide on standard way using tool
      - evaluate the pilot project vs its objectives
- - - - search for defects
      - verifies the functioning of sw components
    - - test interface between components
      - interaction to different parts of system
        (OS, file,, hardware, between systems)
    - - behavior of whole system by scope of development project
      - verification requirement specification
    - - validation testing with respect of
        [user need, requirement, business process]
- - - - : black-box testing
        (specification based testing)
      - can be experienced-based
    - - interaperability
      - security
      - accuracy
      - complicance
    - - requirement-based
      - business-process-based
  - - - performance
      - load
      - stress
      - usability
      - maintaining
      - reliability
      - portability
  - - - any test level
      - mostly at
        
        component
        
        based on architecture system
        
        code coverage
        
        intergration
  - - - confirmation testing
        (re-testing)
        
        test fail -> fix -> test again with same way as first time {input, data, env}
      - regression testing
        
        verify that modification in software
        
        not cause unintended adverse side effects
        
        system still meet requirement
        
        be executed whenever software changes
- - - - plan enhancement changes
      - corrective & emergency changes
      - change of env (OS, DB,...)
      - 2 types
        
        planned modificatioons
        
        identified
        
        perfective modification
        
        adaptive modification (env change)
        
        corrective planned modification (deferrable correction of defect)
        
        Ad-hoc corrective modification
    - - operational testing
        
        new environement
        
        changed software
- - - - -> user test technique
        
        2. Structure-based
        (white-box)
        
        2 purpose
        
        test coverage measurement
        
        structural test case design
        
        Test coverage
        
        define
        
        type
        
        statement coverage
        
        decision coverage
        
        branch coverage
        
        sub-technique
        
        statement
        
        decision
        
        condition
        
        multiple condition
        
        1. Specification-based
        (black-box)
        
        equivalence partitioning
        
        boundary value analysis
        
        decision tables
        
        combination of inputs | stimuli (cause)
        
        state transition testing
        
        execute valid/ invalid state
        
        3. Experience-based
        
        techniques
        
        error guessing
        
        depend on skill of tester
        
        no rule for error guessing
        
        fault attack
        
        exploratory testing
        
        informal test design
        
        tester actively control + perform test case
        --- user info gain ---> design new + better tests
    - - based on test strategy / detailed test approach
      - list things that we could test
      - can be identified for test data, test input, test outcome