Guardian Command (GC)

Guardian Command (GC)

1. 2. Divide testing by Risk Analysis

   • High Risk - any process, feature or functionality that is essential to the customer's need. Business Critical Processes.
   • Medium Risk - failure of any process, feature or functionality will cause severe disruption to the customer.
   • Low Risk - failure of any process, feature or functionality may have a workaround or disruption to the customer is not severe.
   • 1. Test Requirements
     • • Unit tests at program code level to verify no bugs have been introduced.
     • • Functional testing - all functions like call logging, resource allocation, alerts etc.
     • • Integration testing - testing combination of modules like call monitoring & planned incidents.
     • • Regression testing - continuously test to check for defects introduced as a result of changes in successive builds.
     • • System testing - verify GC as a whole meets the specified requirements.
     • • Compatibility Testing - verify GC works with ICCS, IRS and Modas systems on all supported platforms.
     • • Performance Testing - GC's performance under different pay load conditions simulating different customer environments.
     • • Load Testing - stress GC to simulate anticipated peak load conditions.
     • • Endurance Testing – test GC for weeks or months on end to highlight any system crashes, system not responding or memory leak issues. After long periods of sustained activity is GC reliable, stable and performing to our expectations?
     • • Exploratory Testing - test design and test execution at the same time. Test free-form while you explore GC.
     • • End-to-End Testing - test GC workflow from start to end, representing what a customer would do to complete a task or business process.
     • • User Acceptance testing - test and confirm GC is fit for purpose and meets all user requirements.

2. Test Data

   • Configuration Data
   • Baseline Data Set
     • Different sets to represent different customer size and configurations.
     • Data Comparison tests run during regression testing.

3. Manual Testing

   • Exploratory Testing
   • User Acceptance Testing
   • Compatibility Testing
   • End-to-End Testing
   • Installation & configuration

4. Automated Testing

   • Functional, Integration, Regression, System, Performance, Load & Endurance Testing.
   • Using Test Data for GC System Configuration Testing.
   • TestComplete
     • Brainstorming for Smart Test Design
       • Tests broken into minute tests like test login, test log out etc.
         • Use Batch feature to group small tests to make any combination of tests.
           • Test Design Techniques
             • • Static techniques like technical reviews, informal reviews, inspections.
             • • Dynamic structure based techniques like statement, decision or condition coverage.
             • • Dynamic experience based techniques like exploratory testing or error guessing.
             • • Dynamic specification based techniques such as use case testing, decision table testing and equivalence partitioning or boundary value analysis.
     • Use Data Driven and Distributed testing features for Performance, Load & Endurance Testing.
     • Use Keyword Testing for Functional and Regression testing.
     • Data Driven tests include valid data and invalid data formats.
     • Checkpoints
       • Compare, Verify or Update