Please enable JavaScript.

Coggle requires JavaScript to display documents.

5.3 (Other types of testing (White box testing (test that assesses the…

- - - - The first stage, called alpha testing, is often performed only by users within the organization developing the software (i.e., systems testing).
      - second stage, called beta testing, a form of UAT, generally involves a limited number of external users.
        
        involves real-world exposure, sending the beta version of the product to independent test sites or offering it FREE to interested users.
  - - - It is not meant to replace other testing methods, but rather to provide a LIMITED EVALUATION of the system.
      - POCs are early pilot tests—usually over interim platforms and with only basic functionalities.
  - - - test data are used in determining procedural accuracy or conditions of a program’s specific logic paths (i.e., applicable to unit and integration testing).
  - - - without regard to any specific internal program structure
  - - - to ensure that the software that has been built is traceable to customer requirements (i.e., Are we building the right product?)
  - - - data used in regression testing should be the same as the data used in the original.
  - - - purpose of parallel testing is to determine whether the new application performs in the same way as the original system and meets end-user requirements
  - - - should cover the platform that will perform primary application processing and interfaces with other systems
      - in a client server or web development, those that perform changes to the desktop environment.
- - - - uses a set of test cases that FOCUS ON THE CONTROL STRUCTURE OF THE PROCEDURAL DESIGN.
      - ensure that the INTERNAL OPERATION OF THE PROGRAM PERFORMS ACCORDING TO SPECIFICATION
  - - - objective
        
        is to take unit-tested modules and
        BUILD AND INTEGRATED STRUCTURE DICTATED BY DESIGN .
      - used to refer to tests that VERIFY AND VALIDATE THE FUNCTIONING OF THE APPLICATION under test WITH OTHER SYSTEM ,
        
        in which a set of data is transferred from one system to another
  - - - specific analyses may
        be carried out during system testing: ReSeLoVoPeSt
        
        – Recovery testing—
        
        Checking the system’s ability to recover after a software or hardware failure
        
        – Security testing—
        
        Making sure the modified/new system includes PROVISIONS FOR PROPER ACCESS CONTROLS and does not introduce any security holes that might compromise other systems
        
        – Load testing—
        
        Testing an application with LARGE QUANTITIES OF DATA to evaluate its PERFORMANCE DURING PEAK HOURS
        
        – Volume testing -
        
        Studying the impact on the application by testing with an INCREAMENTAL VOLUME OF RECORDS to determine the maximum volume of records (data) the application can process
        
        – Stress testing—
        
        Studying the impact on the application by testing with an INCREMENTAL NUMBERS OF CONCURRENT USERS/SERVICES on the application to determine the maximum number of concurrent users/services the application can process
        
        – Performance testing—
        
        Comparing theSYSTEMS'S PERFORMANCE TO OTHER EQUIVALENT SYSTEM'S PERFORMANCE using well-defined benchmarks
  - - - quality assurance testing (QAT),FOCUSING ON TECHNICAL ASPECTS OF THE SYSTEM , PERFORMED BY IT DEPARTMENT
        
        focuses on the documented specifications and the technology employed.
        
        verifies that the application works as documented by TESTING THE LOGICAL DESIGN AND THE TECHNOLOGY ITSELF
        
        ensures that the application MEETS the documented TECHNICAL SPECIFICATIONS and DELIVERABLE
      - UAT, focusing on functional aspects of the
        application.
        
        process of ensuring that the system is production-ready and satisfies all documented requirements.
        
        • Definition of test strategies and procedures
        
        • Design of test cases and scenarios
        
        • Execution of the tests
        
        • Utilization of the results to verify system readiness
        
        UAT plan must be documented for
        the final test of the completed system.
        
        tests are written from a user’s perspective and should use the system in a manner as close to production as possible.
        
        new business process has been developed to accommodate the new or modified system, it should also be tested at this point.
        
        to verify that supporting processes integrate into the application in an acceptable fashion.
        
        should be performed in a secure testing or staging environment.
        
        secure testing environment, in which both source code and executable code are protected,
        
        helps to ensure that unauthorized or last-minute changes are not made to the system without going through the standard system maintenance process.
        
        UAT of acquired systems
        
        systems and any subsequent changes should be tested thoroughly by the END USER AND SYSTEM MAINTENANCE STAFF .
        
        ensure that programs function as designed by the vendor and the CHANGES DO NOT INTERACT ADVERSELY WITH EXISTING SYSTEM
        
        absence of controls, the RISK of introducing MALICIOUS PATCHES/TROJAN HORSE programs is very high
- - - - Objective:- assessment of the effectiveness of the security controls and processes to be deployed.
        
        the RISK ASSESSMENTS performed
        
        and TEST PLANS
        
        reviewing SECURITY PLANS
  - - - has implemented appropriate CONTROLS ,
      - meets the BUSINESS REQUIREMENTS
      - is READY TO BE MIGRATED to production.
    - - should identify and EXPLAIN THE RISK that the organization is taking by implementing the new system.