Test Environment. A test environment is made available to Customer. Customer is responsible for providing test cases and data and is also responsible for test implementation. Customer is also responsible for notifying Service Provider upon test completion. Test support is provided during Service Desk hours on a case by case basis only. Priority will always be given to production operations. If Customer wishes to procure test support, then it may initiate a Service Request for this purpose.
Test Environment. Q2’s Pre-Production Test Environment is the build-out of a test system for Customer by Q2 during the pre-implementation phase of deployment and includes hardware, installation and maintenance of a production-like environment and connectivity to test Customer’s core prior to Commencement Date and includes. Q2’s Post-Production Test Environment is the build-out of a test system for Customer by Q2 and includes hardware, installation and maintenance of a production-like environment and connectivity to test Customer’s core.
Test Environment. Atlas also offers an optional Test Environment Server Hosting option. This option is for sites who anticipate making frequent changes to their Ares setup, have special setup customizations (such as authentication or links to external systems), or for sites that want to test new releases before using them in production. The Test Environment Server Hosting provide a second server to be used to test system changes and new releases outside of the standard production environment. This still includes all server setup, upkeep, and backup, as well as all operating system maintenance. In addition, upon the request of the site, Xxxxx will sync the Test Server to the Production server when new releases are installed. This is an optional setup and not required if you choose the Production Environment Server Hosting.
Test Environment. In rare cases, personal data is processed in a test environment, and when used, the requirements for the security level are the same as described in this instruction. Test environments are physically separated from production environments.
Test Environment. The Contractor shall perform test environment setup and coordinate unit testing, integration testing, system testing, regression testing, and performance/load testing. As required, the Contractor shall create a CR for test configurations and data scripts for test events. The Contractor shall use the software development environment to perform unit testing. Upon successful completion of unit testing, the Contractor shall provide test results for IV&V. The Contractor shall maintain CM of the code used for System Integration Testing (SIT) and GAT and coordinate Government involvement to perform SIT. Following successful completion of SIT, the Contractor shall assist in configuring the PSS for GAT. The Contractor shall identify requirements and associated schedule for technical refresh of these environments as part of the maintenance function. The Contractor shall maximize use of existing GCSS-MC facilities, software tools, and other Government developmental and integrated resources to reduce costs. The Contractor shall produce a report using GFI provided HP ALM when directed by the Government. The Contractor shall implement tools and methods that provide a complete detailed record of test documentation and provide data compatible with Government systems and accessible to Government designated personnel. The Contractor shall implement tools and methods that provide a complete record of test documentation. The Contractor shall identify and ensure test environments contain required test data necessary to facilitate operationally relevant (realistic) test and evaluation. The Contractor shall include procedures for test data cleansing, conversion, and verification/validation, as necessary. This data shall be transferrable and in a form usable by the Government.
Test Environment. The Customer undertakes to maintain an operational test environment that is representative of its production environment, on which the Service Provider can operate directly by remote access made available by the Customer, at its own cost. In the test environment maintained by the Customer, the Customer provides the Service Provider with a work space representative of the production work spaces, which can be used by the Service Provider for Maintenance.
Test Environment. The following parameters should generally be recorded during characterization and may be used to de-rated data to standard values:- • Altitude (sea level) • Air humidity (50% +/- 10%) • Inlet Air Temperature (0oC to +50oC)
Test Environment. • The system should provide uniform airflow across the vent opening and be of constant volume airflow. • Altitude (sea level) • Air humidity (50% ± 10) • Inlet Air temperature (0°C to +50°C) • Minimum airflow (0.5ms-1) • Maximum airflow (3ms-1)
Test Environment. Customer shall maintain (i) a test environment for the Supported Software and the ability to update the test environment from production when issues occur to enable Blue Yonder to diagnose and research support issues, (ii) remote/VPN access as requested by Blue Yonder to enable Blue Yonder to diagnose and research support issues, and (iii) a Blue Yonder log-on code that will allow Blue Yonder access to Customer's application environment to support both the Customer server and database software. This remote sign-on capability may be used to allow access to Customer's system to enable Blue Yonder to provide diagnostic and problem- solving assistance. The remote sign-on capability may also be used by Blue Yonder's other services, customer support or product development staff to deliver custom enhancements or modifications, if any, to be provided pursuant to a written agreement bet ween Blue Yonder and Customer. Remote access is controlled by Customer who will, where appropriate, authorize Blue Yonder's access to its system and pay any related connectivity charges.
Test Environment. During the term of this Agreement, AssetWorks will maintain a test environment in addition to the production environment. New Software releases or patches are first introduced to the test environment, and it is Client’s responsibility to perform testing and report any errors within ten (10) days. If Client does not report any errors within ten (10) days, the new Software release or patch will then be discharged in the production environment. AssetWorks may use the test environment to trouble shoot or configure and test new functionalities or reports. If Client requests for AssetWorks to synchronize data between the test and production environments, additional fees will apply.
