Please enable JavaScript.

Coggle requires JavaScript to display documents.

Test types, Maintenance testing, Black-box testing - specifiction based…

- - - - Test objectives: evaluating completeness, correctness, appropriateness.
        
        Focusing on suitability, interoperability, security and compliance
        
        Requirements-based or business-process-based (user stories) Work products: functional requirements, business requirements specification, epics, user stories, use cases, functional specification, or undocumented.
        
        At component test level, functional testing can be based on component specification
        
        Create List of items to test / not to test (table of contents)
        
        Prioritize based on risk criteria
        
        Coverage measure based on elements of the function that we can list (all of the options). If our test set has at least 1 test for each option - coverage is 100%
        
        Functional coverage - percentage of the type of element (of particular functionality) being exercised by test
        
        Traceability between our tests and functional requirements (can identify gaps)
    - - Test objectives: evaluating reliability, performance efficiency, security, compatibility, and usability.
        
        Non-functional includes: performance, load, stress, usability, maintainability, reliability, portability and security testing.
        
        ISO standard - classification of software product quality characteristics
        
        Non-functional coverage - percentage of the type of non-functional element being exercised by test
        
        Traceability between our tests and functional requirements (can identify gaps)
        
        Portability test - to check if system works on all supported OS
    - - Test objectives: evaluating structure or architecture of the component or system is correct, complete, and as specified
        Internal structure: code, architecture, work flows, data flows within the system.
        
        Thoroughness of testing measures through the coverage of a set of structural elements or coverage of testing. Percentage of executable elements that have been exercised (covered) by a test suit
        
        For acceptance level, white-box type can be applied to check if all work process flows have been covered
    - - Confirmation testing
        (re-testing) - after fixing defect. The objective is to confirm that failures caused by those defects do not occur anymore.
        
        Can follow bug report step by step with same data, environment to verify, and extend to another parts related to this defect
      - Regression testing
        
        Regression tests are executed whenever the software changes, either as a result of fixes, new or changed functionality. Environment changes like new version of the host operating system or production environment has a new version of Java Virtual Machine.
        
        Regression test suits - set of test cases designed to collectively exercise most functions in a system (certainly the imported ones). But not test anyone in detail.
        
        We can have regression test suit at every test level
        
        If regression suit is to large - make a subset of regression tests. In Agile development - the subset would be chosen in order to meet the particular iteration objectives. The selection should be made considering the latest changes that have been made to the software
        
        If set to large, we can eliminate low risk test cases or the ones that cover same test condition or test cases that can be combined (if they are always run together)
        
        1 more item...