API Readiness
September 18, 2015
Software Testing Types
September 18, 2015

Testing Lifecycle

cEpoch’s test suite enables clients to manage testing life cycle with relative ease and accuracy. The product suite is meticulously designed to support full life cycle of the application module taking the special circumstances of the each phase of the life cycle.

Initial Migration Testing

During initial migration of any application or system the test automation suite will be configured to understand the inner functioning of the application under test.  These configurations and deliberate setting will make the testing automation product adapt to the environment. In the phase, the test expert partnering with client SMEs will identify solid candidate test cases for automation and prepares relevant test data and expected results to fulfill business requirements.

Automated test modules will be configured to provision the test environment will be provisioned in the cloud based on the specifications and capacity parameters defined by the test engineer.

Upon successful instantiation of the test environment and test environment preparations are complete, the test engineer will execute the automated scripts to first baseline the test execution with initial set of data and captures results and builds intelligence to infer user actions and systems behaviors and outcomes.  The captured metadata will be used by the Test Automation system to rerun the scripts unmanned mode for subsequent datasets.  The process also includes to compare the actual results against the intended results and generates disposition report indicating successful or failure of the test cases.

The system has built-in capabilities for logging, notification and reporting of test progress.Any defects will be logged into standard defect tracking solutions such as Bugzilla for further remediation.  The correct components can reenter the testing queue and the same test scripts can be rerun.

In addition, the scripts and driver test data can be migrated to other environments, for example, from test environment to UAT environment and with relative ease the test scripts can be automatically executed in the target environment accelerating the test cycle compression and driving confidence in test accuracy.

This process is repeated until all identified test cases are successfully validated.  Upon completion of the test iteration, another automated module can be invoked to store all configurations, test scripts, results and validations in respective repositories and deallocate the test environment.

Upgrade Testing

System upgrade triggered by hardware and/or software enhancements introduce significant system disruptions and uncertainties.  Upgrades are intended to enhance the application by introducing additional functionality and features to the application or business system. A thorough testing of new modules or functionality along with existing are essential to ensure that the system adequately fulfills the intended objectives.

cEpoch’s test suite is geared to perform this end-to-end testing of the components and modules.  The test engineer can reuse the repeatable test scripts and supplement with new test scripts for enhanced functionality.  The new inventory of test scripts can then be executed on the upgraded application and results can be validated against the expected results.  The enriched test script repository will become input to the next iteration of testing.  As more iterations are added, the size and quality of test script library increases thereby reducing the need for creation of new scripts for subsequent testing.  Hence, repeated usage of cEpoch’s test suite will have inverse relationship to the test cycle time.  Besides compressing the elapsed time of testing phase, cEpoch’s automated test suite will improve testing quality, expand test coverage and releases precious system and functional resources to other high value activities.


Patching is typically performed to remediate identified or potential issues, hot fixes or fix critical error in hardware or software, add new compatible hardware support or security loophole.   Due to criticality and time sensitivity of patching, testing of patches should be completed in a short window without compromising the quality of the deliverable.  Our experience indicates that limited customizations in applications translate into fewer patches, however, we recognize that it may not be practical to restrict client specific custom changes.  Hence, our application is designed to accelerate and efficiently complete test execution for Patching.

cEpoch’s automated suite will be allocated instantly in the cloud and testing team can select the test scripts relevant to the impacted segment of the application and conduct test execution.  This agile approach to test environment setup and test execution saves a valuable time in restoring the system to normalcy after successful patch application.   Our professional team has expertise in identifying the most vulnerable objects of functionality due to patching and increase attention to those elements driving stakeholder confidence. Test execution using cEpoch’s test suite will remove risks and uncertainty associated with patching and brings client’s closer to risk free patch deployment.

For an average patching of an application, our solution will reduce the testing effort by over 80% and client will recognize 75% compression in test cycle duration. Upon validate the test environment will be removed from the cloud instance.

Testing Lifecycle

Leave a Reply

Your email address will not be published. Required fields are marked *