Since partial automation has already taken place as part of BDD and TDD, and is integrated with the CI server, the service level components can be targeted next as the User Interface (UI) is yet to be made available.
Also, there are times when basic UI automation can be accomplished using mocks and stubs. However, the scripts undergo changes once the final UI is ready. The effort to modify the existing scripts is directly proportional to the quality of mocks and stubs that were provided during the initial automation work.
To enable integration, the CI server builds the system on demand, on schedule, or even as soon as the code is checked in.
Each developer can run and test the code on his/her system to ensure that the code is not broken
For an early and extensive integration testing, the test team can utilize the features of service, application, and network virtualization
Whether it is UI integration with service a or database layer, or it is the integration of one...