softwaretesting

Functional - Iterative User Story Testing

The goal of iterative user story testing is to perform validation of partially integrated user stories and uncover defects even before the actual feature is delivered. The approach would require the use of test drivers and test stubs when building out a bottom-up test approach.

The QA team will perform smoke testing of services in the test environment after unit Test results and user story test results are available. Smoke testing will help to identify the initial issues by executing the high level test conditions so that any issues identified in smoke testing can be fixed before starting Iterative user stories Testing phase.

The testing will focus on validating the new features including UI, business rules, DB and interfaces, Workflows and Reports. Validation of features that are not being changed as part of modernization will be covered in regression testing

Product Integration Testing

Product Integration Testing will be done at a logical point where the multiple features are available and delivered for a larger integration test cycle.

Most of the test scripts, automation and service virtualization components will be reused during this phase to enable testing of a complete workflow. 

Though a formal User Acceptance Testing will not be done at this phase, the business users will still be involved to review and provide their inputs on the workflows validated and the test coverage achieved. This is to enable early feedback and ensure any gaps in business understanding are addressed

Functional - Capability Testing

Capability testing is carried out by leveraging the feature test scripts created during the PI sprints. This testing will verify the correct sending and receiving of data across all interfaces relevant to each business process, the correct onward processing of that data and the correct functionality being triggered as a result of the receipt of data.

Where applicable, the QA team would work with other teams, 3rd parties, to orchestrate Capability testing. Virtualized services will be used if integration with 3rd party services if not feasible at the time of testing.

The extent of testing to be done to cover the requirements would be determined by the risk based testing framework. The IT QA team would look to reuse groups of automated test cases designed for Iterative user story testing and feature testing to create the Capability test cases. Before performing Capability Testing, Build Verification Testing will be performed in the identified environment. On successful completion, the End-to-End Testing would commence.

Functional - Parallel Testing

Parallel testing primarily involves executing a workflow through the existing legacy environment and also through the future state distributed environment. The results from both runs are compared to identify differences and then to analyze if those differences are desired results or are defects that require fixes. 

Parallel testing will be performed during different phases of the program, depending on need and relevance. Validation of certain features may require parallel testing. Parallel testing will also be significant while validating the future state platform and while validating the migration of contracts as part of Data Migration testing

Regression Testing

Regression testing will be performed  for every incremental user story test sprint. Automated regression suite will be built during each incremental user story test sprints. This will incrementally build into the master regression pack of the project ready to be used in end to end and implementation test phases.

Regression testing for each testing phase will be performed in their respective environments.

Existing regression assets can also be used where deemed required across all test phases with minimal or no change.

User Acceptance Testing

UAT will be conducted against the defined Business Process. It will not attempt to test the system’s functional details or verify all the possible error conditions, instead selected end to end business processes will be executed, and thereby UAT will feature both the positive and negative testing scenarios. However, the business users can perform random testing outside the formal scripts

Service Virtualization

Virtualization enables shift left testing approach to avoid dependency on unavailable functionalities and environment downtimes, where the services will be connected to virtually created endpoint to test newly created or existing services. We have a dedicated virtualization experts develops the stubs and mocking response that needs to be created wherever necessary as it will be simulating a specific behavioral response to fulfill a certain testing condition or validation checkpoint.  

Cloud Testing

Cloud testing is an integral part of today’s journey to the cloud. We  help you define an effective strategy to test the cloud, so that you can address all the challenges and pitfalls. Software testing in the cloud focuses on functional testing of the application, but it also needs a strong emphasis on non-functional and cloud-specific testing. We adopt this end-to-end approach to ensure high quality across all aspects of cloud implementation.

Scroll to Top