Test Environments. A. Screening Testing: regular testing of asymptomatic individuals that may be among the general community or defined population(s), including:
Test Environments. Motricity currently provides demo environments for testing. If it is determined that additional environment(s) are required for this, then AT&T will reimburse Motricity for all fees associated with building it and will agree to pay Incremental Hardware and Software fees attributed to hosting this additional test environment as business as usual.
Test Environments i. The Contractor shall have at least two (2) testing environments – one for Systems Integration Testing, and one for End to End testing. The environments shall use the appropriate data sets defined by the Department.
ii. The Contractor shall use test environments are compliant with all security requirements defined by North Carolina State and the Department’s Privacy and Security Office to support testing with production data.
iii. The Contractor shall have test environments available prior to conducting Systems Integration Testing.
iv. The Contractor’s test environments must, as appropriate, be able to refresh test environments and ingest files the same size as would be required in a production environment and must be able to use data that would appear in a production environment.
v. The Contractor’s test environment must, as appropriate, be able to simulate date and duration dependent processes.
Test Environments. 3.1 The Contractor’s Test Environments shall be as described in Appendix 2 (Test Environments) and shall meet the requirements of the Test Strategy, Test Approach and the User Integration Performance Measures.
3.2 Unless specifically agreed otherwise with the DCC, the Contractor shall for (and in advance of) each Test Stage:
(a) establish and provide all relevant Test Labs, Test Stubs, Test Environments and Test Data needed to execute the specific Test Specifications (this will include the load and configuration of software code and the creation of databases and transaction files);
(b) specify and build all such Test Labs, Test Stubs, Test Environments for the Contractor Solution in time for each of the relevant Tests as set out in the Test Approach, including procuring and/or installing such Communications Hubs and/or other smart metering or other Hardware as may be required;
(c) provide the number of Test Environments required in order to complete all necessary Testing within the timetable agreed between the parties (including that defined in the Implementation Plan or Test Plan);
(d) provide all reasonably required assistance to the DCC and all other DCC Service Providers in the analysis and resolution of Test Incidents during the System Integration Test Phase; and
(e) provide all reasonably required assistance to all relevant DCC Eco- System Entities (including DCC Service Users) and any other parties participating in User Integration Testing, in the analysis and resolution of Test Incidents during the User Integration Test Phase.
3.3 The Contractor shall be responsible for maintenance and release management:
(a) within the Test Environment used during the System Integration Test Phase; and
(b) within the Test Environments used for UIT Testing and Enduring Testing as agreed with the DCC from time to time (both parties acting reasonably), including in respect of Other ESP Solutions.
Test Environments. 5.2.1 The Service Provider shall provide suitable test Environments for development and Testing of the Service Systems during the Operational Phase.
5.2.2 The Service Provider shall provide a test system and links to the Service Systems, together with associated test/acceptance functions.
Test Environments. (a) Working with other IT teams determine requirements for test environments.
(b) Designing test environments and processes to manage testing in the environments.
(c) Working with server and network teams implement and support the systems infrastructure for test environments (servers, storage, etc.).
(d) Scheduling test environments, negotiating as needed with teams. * Certain information on this page has been omitted and filed separately with the Commission. Confidential treatment has been requested with respect to the omitted portions.
(e) Managing test environment data setup and refresh as required by the teams.
Test Environments. 10.3.1 The Service Provider must provide the Authority with access to the following environments throughout the testing lifecycle: System or In-Sprint Test Environment(s) System Integration Test (SIT) Environment User Acceptance Test (UAT) Environment Operational Acceptance Test Environment (Non Functional) The Service Provider must also accommodate any required Data Refreshes / Cleansing activity within these environments to support the test plan.
10.3.2 During the integration Test Levels (SIT & UAT), the Service Provider must work closely with the System Integrator and Authority to ensure the end-to-end functionality is working as expected.
Test Environments. All applications have separate testing environments. Testing environments do not contain production data. Test environments can be used to showcase upcoming features and to test new functionalities.
Test Environments. Different test sites located in Netherland (Orbis) and in Switzerland (MRPS) will be involved in the Miraculous-Life project. User needs and requirements analysis and user pre-trials evaluation will be realized in a laboratory setting and/or in the users’ apartment, while the trials will be performed in the users’ apartment. As the prototypes will be installed in the users’ apartment, specific ethical and legal issues will be considered. Finally, investigators will ensure that test locations are safe and comfortable for both involved participants and caregivers.
Test Environments. When delivered as a Cloud Application, a test environment can also be supplied and managed by Decos: you need to purchase maintenance for these test environments. Each new Version is installed by Decos in the test environment of the Client. Tickets that you report as a result of disruptions in the test environment will be treated as regular Tickets by Customer Support. These Tickets are given ‘low’ priority because there is no disruption of the process (yet). For shared Cloud applications (‘public cloud’), all clients work in the same Version. No test environments are offered for these Applications.
