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.
...
HTML |
---|
<img src="https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/FUNCgroup_master_20-builds_graph.jpg", alt="FUNCgroup", style="width:525px;height:350px;border:0"> |
commit 7981a32f37d64225a5b641725ba172cdc32e2f0d 92cc2685593d51fe26360913592279aa327182b5 (HEAD -] master, origin/master, origin/HEAD)
Author: Ray Milkey [ray@opennetworking.org]
AuthorDate: Thu Fri Aug 16 1417 10:5507:46 57 2018 -0700
Commit: Ray Milkey Thomas Vachuska [ray@opennetworkingtom@opennetworking.org]
CommitDate: Thu Fri Aug 16 2317 17:5251:44 20 2018 +0000
Fix NPE when component can't be found
remove redundant definition for ONOS_VERSION
Case 1: Pull onos branch and build onos on Teststation. - PASS
...
- 1.1 Constructing test variables - PASS
Case 2: Starting up 1 node(s) ONOS cluster -
...
PASS
Set up ONOS with 1 node(s) ONOS cluster
- 2.1 Apply cell to environment - PASS
- 2.2 Uninstalling Atomix - PASS
- 2.3 Uninstalling ONOS package - PASS
- 2.4 Creating ONOS package - PASS
- 2.5 Installing Atomix - PASS
- 2.6 Installing ONOS package - PASS
- 2.7 Set up ONOS secure SSH - FAIL
- Test step FAIL
- PASS
- 2.8 Checking ONOS service - FAIL ONOS service did not start properly on all nodes
- PASS
- 2.9 Starting ONOS CLI sessions - PASS
- 2.10 Checking ONOS nodes - FAIL Not all ONOS nodes are in READY state
- PASS
- 2.11 Checking ONOS applications - FAIL Not all ONOS apps are activated
- PASS
Case 3: Compare ONOS Topology view to Mininet topology -
...
PASS
Compare topology elements between Mininet and ONOS
- 3.1 Copy Mininet topology file - PASS
- 3.2 Setup Mininet Topology - PASS
- 3.3 Assign switch to controller - PASS
- 3.4 Comparing Mininet topology to ONOS topology - FAIL
- ONOS incorrectly discovered the topology
- PASS
- 3.5 Create hosts and start scapy - No Result
- 3.6 Start scapy components - PASS
Case 5: Verify Group of type All are successfully Added - PASS
Install a Group of type ALL Verify the Group is Added Add a flow using the group Send a packet that verifies the action bucket of the group
- 5.1 Add Group using Rest api - PASS
- 5.2 Check groups are in ADDED state - PASS
- 5.3 Adding flow with Group using rest api - PASS
- 5.4 Testing Group by sending packet using Scapy - PASS
Case 6: Delete the Group and Flow added through Rest api - PASS
- 6.1 Deleting Group and Flows - No Result
...
- 6.2 Deleting the created flow by deviceId and flowId - PASS
- 6.3 Deleting the created group by deviceId and appCookie - PASS
Case 7: Verify Group of type INDIRECT are successfully Added - PASS
Install a Group of type INDIRECT Verify the Group is Added Add a flow using the group Send a packet that verifies the action bucket of the group
- 7.1 Add Group using Rest api - PASS
- 7.2 Check groups are in ADDED state - PASS
- 7.3 Adding flow with Group using rest api - PASS
- 7.4 Testing Group by sending packet using Scapy - PASS
Case 6: Delete the Group and Flow added through Rest api - PASS
- 6.1 Deleting Group and Flows - No Result
- 6.2 Deleting the created flow by deviceId and flowId - PASS
- 6.3 Deleting the created group by deviceId and appCookie - PASS
Case 10: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 10.1 Stopping and Removing Scapy Host Components - PASS
- 10.2 Stopping Mininet - PASS