Please enable JavaScript.

Coggle requires JavaScript to display documents.

Software Testing and Analysis calidad - Coggle Diagram

- - - - Module
        
        Test checks module behavior against specifications or expectations
      - Integration
        
        Test checks
        module compatibility
      - System
        
        Tests check behavior of the whole system respect to specifications
      - Acceptance test
        
        Tests check behavior of the whole system respect to user needs
  - - - The most effective way to ensure that the system test suite is not unduly
        influenced by design decisions is to design most system test cases as early as possible
    - - Chipmunk development of Web-based purchasing
        
        Each of these scenarios became
        a system test case specification
        
        Several of the system test scenarios simulated in earlier integration tests
    - - To make diagnosis of failed test executions as clear and simple as possible
  - - - It may take a very great deal of testing to obtain evidence of a sufficient level of relia- bility.
  - - - With usability checklists. Inspection provides early feed-
        back on usability
    - - With end users to explore their mental model , evaluate alternatives , and validate software usability
    - - With both usability experts and end users to monitor
        progress and anticipate usability problems
    - - That includes expert-based inspection and testing
  - - - We say that the new version regresses with respect to former versions
      - A simple approach to regression testing consists of reexecuting all test cases designed for previous versions
  - - - The number of tests to be reexecuted may be large, especially for legacy software
    - - Executing all of them eventually but reducing the frequency of those deemed least likely to reveal faults by some criterion
      - Regression test selection techniques are based on either code or specifications
    - - Regression techniques are based on the differences between the CFGs of the new and old versions of the software
    - - Ccompare the annotated control flow graphs of the two program versions
      - Identify a subset of test cases that traverse modified parts of the graphs
  - - - System requirements include many nonfunctional behavioral properties.
      - Selective regression test selection based on analysis of source code is now well-
        studied
      - Increasingly ubiquitous network access is blurring the once-clear lines between
        alpha and beta testing
    - - Musa [Mus04]
        
        Guide to reliability engineering from a pioneer in the field
      - [GHK+98] and Rothermel
        
        Useful overviews of selective regression testing
    - - Define at least one test case
        that may serve both during final integration and early system testing
      - Provide two or more examples of resource limitations that may impact system
        test more than module and integration test. Explain the difference in impact.
- - - - Chipmunk Web
        
        Envisage at least one situation in which thread integration should be preferred over critical mod- ule and one in which critical module testing should be preferred over thread
      - Backbone testing strategy yield savings in the cost of producing test scaffolding, relative to other structural integration testing strategies
      - COTS
        
        During integration testing, the program failed when
        reading an empty file and when reading a file containing a syntax error.
    - - The buffer overflow problem in libpng
        
        Vulnerability Note VU#388984 [Uni04]
      - Ariane 5 failure [Lio96]
        
        Several sources on the Web
      - Mars Climate Orbiter [Ste99]
        
        Web
    - - Analysis of components and component-based systems in one environment
        
        Produce useful information for assessing likely suitability for using some of the same components in another environment
      - Software design for testability is an important factor in the cost and effectiveness
        of test and analysis, particularly for module and component integration
    - - A component designed for wide reuse will usually be much more complex than a module designed for a single use
      - A reusable component is by definition developed without full knowledge of the environment in which it will be used
  - - - Module
        
        Test checks module behavior against specifications or expectations
      - Integration
        
        Test checks
        module compatibility
      - System
        
        Tests check behavior of the whole system respect to specifications
      - Acceptance test
        
        Tests check behavior of the whole system respect to user needs
  - - - Driven partly by the needs of test
      - Big bang approach
        
        Neither stubs nor drivers need bebig bang testing constructed
        
        Requiring the whole system to be available before integration does not allow early test
        and feedbac
        
        Waiting until all mod- ules are integrated, and testing them together