Functional Tests Sample Clauses

Functional Tests. TVA will perform IP Product testing by issuing Test Interruptions to all IP5 participants (Reliability Only Fleet). The Reliability Only Fleet will be tested as illustrated in the following schedule: LPC T&C Rolling (7/27/18) Fleet Test Schedule Test Interruptions will occur during the Summer Period or Winter Period Test Interruptions will occur during the Summer Period or Winter Period Test Interruptions will occur during the Summer Period or Winter Period Additional Tests by Request Customers with <100% Performance Factor in latest fleet test may request retest for protected demand reinstatement (at TVA’s discretion) Customers with <100% Performance Factor in latest fleet test may request retest for protected demand reinstatement (at TVA’s discretion) Customers with <100% Performance Factor in latest fleet test may request retest for protected demand reinstatement (at TVA’s discretion)

Functional Tests. This section reports the set of main functional tests performed during the implementation of the VRM Resource Manager modules. In particular, Table 4-1 and Table 4-2 describe the test set for the RDT module (as part of the Resource Manager) and the MDA, respectively. Descriptors Translation Translation of descriptors for VNF, PNF and NS from ETSI SOL-006 to TMF 633 and 634 Yes RSOC invocation Invocation of the RSOC to store the translated services/resources Yes Receiving a monitoring spec The module receives, from Vertical Slicer, a configuration containing the metrics to monitor, the duration of the monitoring stage, and the unique identifiers associated with the operator and business flow ID. Yes Collecting values of the monitored metrics The module collects metric values, from OSM, within the step received from the monitoring spec. Yes Pushing data into a ▇▇▇▇▇ topic The module, after signing the collected data, that is, performing the hashing and encryption operations, pushes it into a ▇▇▇▇▇ topic. Yes

Functional Tests. Functional tests are run during a version change of the software to assess the quality of the version being built. The modification of the source code or the release of a new version does not mean that the code is deployed to the production system. The production manager or a representative responsible for the software is required to trigger the deployment manually.

Functional Tests. The set of functional tests conducted so far on the NSSO are reported in Table 4-3. Name Description Passed (Yes/No/Partially) Service instantiation A simple service instantiation is requested from the ISSM. The NSSO provisions a network slice with one network service relying on the local domain functionality. Yes Configuration of monitoring metrics The NSSO requests the configuration of the metrics to the MDA Yes

Functional Tests. Contractor shall include Functional Tests on the Project Schedule and shall perform and successfully complete each of the Functional Tests described in Appendix E.

Functional Tests. The functional tests (see Table 2-6) carried out on this module are mainly related to the verification of the correct functioning of the implemented methods. Module setup The module can be automatically installed and configured. Yes Client addition A new client is connected to the VPN, obtaining a client IP in the VPN. Yes Client removal A client is disconnected, removing its IP from the known list. Yes Connection establishment The automated connection establishment between two VMs running in different subnets is tested. Yes Connection deletion In the current design we use the public key to search for the client to be removed. Yes

Functional Tests. The following functional tests shall be performed after the equipment has been energized, but before the generator is paralleled with PacifiCorp's system: 1. Check that each protective relay trips the appropriate generator breaker and/or main breaker. 2. When first energized, check that proper secondary potential is applied to all voltage and frequency relays. 3. Check the generator phase rotation. (PacifiCorp's phase rotation is A B C counterclockwise). 4. Check protection and control systems are functioning properly.

Functional Tests. The following table describes several functional features which allow checking the proper behaviour of different modules and activities carried out by the Trust Management Framework. It should be noted that all the tests described in Table 2-2 are not related to the integration of the Trust Management Framework with other 5GZORRO modules. Therefore, the following tests are internal to the TMF. Trust Parameters Verify whether the dictionary received as parameter complies with the format of the described trust information model Yes Start data collection Verify that The Trust Management Framework is able to create a new pipeline in ▇▇▇▇▇ Yes Receive information from a topic Verify that The Trust Management Framework can retrieve trust information from a particular stakeholder to compute a trust score. Yes Send information to a topic Verify that The Trust Management Framework is able to push information to a ▇▇▇▇▇ topic and also to the Data Storage in order to keep track of a trust relationship. Yes

Functional Tests. Final Completion of the Facility requires successful completion of Functional Tests as further detailed herein: