-
Notifications
You must be signed in to change notification settings - Fork 3
Test 01 02
Bruno Garcia edited this page Feb 11, 2021
·
4 revisions
Test Case Name | Basic facility configuration | Test Case id | Test-01-02 |
---|---|---|---|
Test Purpose | Verify that the ELCM correctly reads the Facility Registry | ||
Configuration | |||
Test Tool | FIle system, Web browser | ||
Metric | |||
References | |||
Applicability | ELCM | ||
Pre-test conditions | Test-01-01 has been completed successfully. | ||
Test sequence | Step | From the Additional Resources section below, download the provided files |
|
Step | Save the simpleResource.yml file on the Resources subfolder of the ELCM |
||
Step | Save the simpleScenario.yml file on the Scenarios subfolder of the ELCM |
||
Step | Save the simpleTestCase.yml file on the TestCases subfolder of the ELCM |
||
Step | Save the simpleUE.yml file on the UEs subfolder of the ELCM |
||
Step | Either restart the ELCM or click on the Reload Facility button of the Dashboard |
||
Step | Review the contents of the Facility Log, ensure that no unexpected messages appear | ||
Step | Using a web browser or a tool similar to curl , access to the facility/scenarios endpoint |
The (raw) response should be similar to {"Scenarios":["SimpleScenario"]}
|
|
Step | Access to the facility/testcases endpoint |
The (raw) response should be similar to {"TestCases":[{"Distributed":false,"Name":"Simple Test Case","Parameters":[],"PrivateCustom":[],"PublicCustom":false,"Standard":true}]}
|
|
Step | Access to the facility/ues endpoint |
The (raw) response should be similar to {"UEs":["SimpleUE"]}
|
|
Test Verdict | If no unexpected issues arise, then the ELCM loaded the facility information correctly and the facility endpoints are available | PASS | |
Additional Resources | simpleResource.yml - simpleScenario.yml - simpleTestCase.yml - simpleUE.yml |