Definition
An environment is a user-defined collection of resources that host an application. There are four typical
environments:
Development (DEV)
In the Development environment, developers build and deploy code in a test lab, and the development team tests the
application at the most basic level. When the application meets certain criteria for advancement, it moves to the next
environment.
System Integration Testing (SIT)
In the System Integration Testing environment, the application is tested to ensure that it works with existing
applications and systems. When the application meets the criteria of this environment, it’s deployed to the next
environment.
User Acceptance Testing (UAT)
In the User Acceptance Testing environment, the application is tested to ensure that it provides the required features
for end users. This environment usually is production-like. When the application passes these requirements, it’s
promoted to the final environment.
Production (PROD)
In the Production environment, the application is made available to users. Feedback is captured by monitoring the
application’s availability and functionality. Any updates or patches are introduced in the DEV environment and follow
the same cycle.
Environments in IBM Rational Solutions
Both UrbanCode and Rational Test Workbench have some understanding of environment. UrbanCode Deploy understands the hosts,
components, and deployment processes. Rational Test Workbench understands the hosts and data required to execute
the test stubs or run tests.
An environment in Rational Integration Tester (RIT) is a set of variables (tags) and bindings that can be used
to provide runtime configuration settings to test resources. By creating multiple environments (for example, "System
Test", "UAT"), you can quickly run the same set of test resources against different phases of your product lifecycle.
For example, environment tags can be used to modify messaging settings, such as port numbers.
