Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
Work in Progress
Objectives: Test onos on the platform level:
- Pull latest onos (image, tar ball, etc)
- Starting up onos
- Form a cluster
- Activate and deactivate applications after startup
Test Suite: PLATdockertest
| Test Cases # | Description | Pass/Fail Criteria | Implementation Status |
|---|---|---|---|
| 1 | Set up test parameters | pass: if params are set | Production |
| 1000 | pre-test clean env: delete onos containers if exist; delete images with <none>:<none> tag if exists (seems to be some docker issue labeling image with this tag) | pass: if no containers in docker and no images in docker | Production |
| 5 | pull "onosproject/onos:latest" image from docker repo | pass: if image is pull | Production |
| 10 | start three onos containers as standalone onos and obtain IPs of all nodes | pass: if onos node IPs are obtained | Production |
| 110 | Step1: check standalone apps status | pass: if "drivers" app in ACTIVE state AND all builtin apps in "INSTALLED" state | Production |
| Step 2: form onos cluster with all nodes | pass: if onos form cluster with correct number of nodes | Production | |
| Step 3: check cluster startup apps status | pass: f "drivers" app in ACTIVE state AND all builtin apps in "INSTALLED" state | Production | |
| Step 4: activate "proxyarp" and "fwd" apps and check apps status | pass: if newly activated apps in "ACTIVE" state | Production | |
| Step 5: deactivate "proxyarp" and "fwd" apps and check app status | pass: if newly deactivated apps in "INSTALLED state | Production | |
| 900 | check onos log for exceptions after test | WIP | |
| 1000 | post-test clean env | pass: if no containers and images left | Production |