With
the growing complexity of software applications, testing teams face a number of
testing constraints. Such constraints include restricted access to the mainframe
or test environments, unavailability of test data, limited access to third
party systems and economic limitations. More often, constraints are faced when
parallel development teams require access to the same environment. Service
Virtualization is the practice of mocking and stubbing the development and test
environments with realism in order to optimize the development time and shift
left testing. All this is done with the sole agenda for a faster release
process and higher quality delivery.
A
Service Virtualization Strategy works on the following approaches for
eliminating Software Testing Constraints and establishing Independent testing.
1. Creation
of Live Environment:
Service Virtualization needs to be applied at or between any layer where
dependencies exist in order to provide the most realistic or live-like possible
environment. Mostly, teams try to move forward with their own component
development by stubbing the next downstream system only. Alternatively, when
teams work with real data scenarios, the resulting environment is more
realistic and current than manually coded stubs.
Benefits:
o
Ability
to start development despite the unavailability of the system interface.
o
Reduced
cycle time for test execution.
o
Improvement
in test coverage because of reduced data dependency and available testing time.
o
Improvement
in unit testing with lesser effort.
o
Improvement
in code quality due to increased test coverage and regression testing.
o
Ability
to build a simulator with a low maintenance effort.
2. Enabling
Parallel Devlopment and Testing: Service Virtualization enables the development and
testing team to work simultaneously by acting as a ‘go between’ asset between
the system under development and the system under test in a symbiotic manner.
Such a solution allows teams to execute under live services where they are
available, functionally robust and data synchronized. For situations where the
teams do not have the services that support the component correctly, they can
switch back to virtual services. This ability to switch between a purely
virtual system and a live system is a very powerful asset in creating a robust
parallel development capability.
Benefits:
o
Increase
in the speed of test and development cycles.
o
True
responsiveness of Agile Iterations.
o
Reduced
burden of Version control.
o
Increase
in issue acceptance and resolution prior to production.
Read More ...
No comments:
Post a Comment