Versions Compared

Old Version 756

changes.mady.by.user Jenkins Technical User

Saved on

compared with

New Version 757

changes.mady.by.user Jenkins Technical User

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

HTML
<img src="https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/FUNCintentRest_master_20-builds_graph.jpg", alt="FUNCintentRest", style="width:525px;height:350px;border:0">

commit 42e8c2527e3877511d061ef28b228e25e12a4c72 0af65230b9772f8463c9fc1374d122693d4f0e63 (HEAD, origin/master, origin/HEAD, master)
Author: Matteo Scandolo alessio [matteoalessio.scandolo@gmailgiorgetti@gmail.com]
AuthorDate: Fri Oct 23 10:17:00 2020 -0700Sat Sep 19 17:06:37 2020 +0200
Commit: pierventre Andrea Campanella [pier@opennetworkingandrea@opennetworking.org]
CommitDate: Sat Wed Oct 24 1028 17:2441:02 17 2020 +0200
Adding helper method in RADIUS packet0000

[ODTN] Interface of a new driver behavior for checking internal connectivity in a device.

Case 1: Pull onos branch and build onos on Teststation. - PASS

...

  • 1000.1 IPV4: Add and test host intents between h1 and h9 - PASS (tick)
  • 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS (tick)
  • 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS (tick)
  • 1000.4 1HOP: Add host intents between h1 and h3 - PASS (tick)
  • 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS (tick)
  • 1000.6 Confirm that ONOS leadership is unchanged - PASS (tick)

Case 2000: Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Rules -

...

FAIL

This test case will test point to point intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Rules

  • 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS (tick)
  • 2000.2 IPV4: Add point intents between h1 and h9 - PASS (tick)
  • 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS (tick)
  • 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - PASS (tick)
  • 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS (tick)
  • 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS (tick)
  • 2000.7 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.8 1HOP: Add point intents between h1 and h3 - PASS (tick)

Case 3000: Single to Multi Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Rules - FAIL

This test case will test single point to multi point intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Rules

  • FAIL (error)
    • Assertion Result for 1HOP IPV4 with no mac address point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Passed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Failed
    • Link Up Scapy Packet Received Passed
    • Remove Intents Passed

Case 3000: Single to Multi Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Rules - FAIL

This test case will test single point to multi point intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Rules

  • 3000.1 NOOPTION: Install and test single point to multi point intents - FAIL
  • 3000.1 NOOPTION: Install and test single point to multi point intents - FAIL (error)
    • Assertion results for IPV4 single to multi point intent with no options set
  • 3000.2 IPV4: Install and test single point to multi point intents - FAIL (error)
    • Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses
  • 3000.3 IPV4_2: Add single point to multi point intents - FAIL (error)
    • Assertion results for IPV4 single to multi point intent with IPV4 type and no MAC addresses
  • 3000.4 VLAN: Add single point to multi point intents - FAIL (error)
    • Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses in the same VLANno options set
  • 3000.5 VLAN: Add 2 IPV4: Install and test single point to multi point intents - FAIL (error)
    • Assertion results for IPV4 single to multi point intent with VLAN treatment

Case 5000: Test host mobility with host intents - PASS

  • 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS (tick)
  • 5000.2 IPV4: Add host intents between h1 and h9 - PASS (tick)

Case 18: Stop Mininet and Scapy - PASS

    • IPV4 type and MAC addresses
  • 3000.3 IPV4_2: Add single point to multi point intents - FAIL (error)
    • Assertion results for IPV4 single to multi point intent with IPV4 type and no MAC addresses
  • 3000.4 VLAN: Add single point to multi point intents - FAIL (error)
    • Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses in the same VLAN
  • 3000.5 VLAN: Add single point to multi point intents - FAIL (error)
    • Assertion results for single to multi point intent with VLAN treatment

Case 5000: Test host mobility with host intents - PASS

  • 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS (tick)
  • 5000.2 IPV4: Add host intents between h1 and h9 - PASS (tick)

Case 18: Stop Mininet and Scapy - PASS

Stopping the Stopping the current mininet topology to start up fresh

...

  • 17.1 Enabling Flow Objectives - PASS (tick)

Case 1000: Host Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Objectives -

...

PASS

This test case tests Host intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Objectives

  • 1000.1 IPV4: Add and test host intents between h1 and h9 - PASS (tick)
  • 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS (tick)
  • 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS (tick)
  • 1000.4 1HOP: Add host intents between h1 and h3 - FAIL (error)
  • Assertion Result for 1HOP for IPV4 same switch
  • Install Intent State Passed
  • Flow duration check Passed
  • Initial Intent State Passed
  • Initial Flow State Passed
  • Initial Ping Passed
  • Link Down Passed
  • Link Down Intent State Passed
  • Link Down Flow State Passed
  • Link Down Topology State Passed
  • Link Down Pingall Passed
  • Link Up Passed
  • Link Up Intent State Passed
  • Link Up Flow State Passed
  • Link Up Topology State Failed
  • Link Up Pingall Passed
    • Remove Intents Passed
  • PASS (tick)
  • 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS (tick)
  • 1000.6 Confirm that ONOS leadership is unchanged - PASS (tick)

...