Conversation
viniarck
left a comment
There was a problem hiding this comment.
Nice to have the tests augmented, overall looks good.
I'll do another pass when the related changes progress too
| intf_id = "00:00:00:00:00:00:00:02:2" | ||
| api_url = KYTOS_API + f'/topology/v3/interfaces/{intf_id}/tag_ranges' | ||
| response = requests.post(api_url, json=payload) | ||
| assert response.status_code == 200, response.text |
There was a problem hiding this comment.
The tag_ranges calls and assertions look good to me. But, this test case test_210_bulk_update_evc was meant only for testing the bulk update of metadata.
Does this test break now with the upcoming changes or was it just extra coverage for tag_ranges? If the latter, then let's move these extra tag_ranges related assertions to another test case.
viniarck
left a comment
There was a problem hiding this comment.
@Ktmi can you also cover resizing tag_ranges with a topology specific test suite? Let's validate both shrinking and growing, while also ensuring that link and interface tag_ranges never overlaps. Cool to also assert the initial link formation inherited/borrowed intersected tag ranges, including also deleting that link. Let's also test a case where tag_ranges vlan of a link don't overlap partially and ensuring it gets the correct expected intersection
viniarck
left a comment
There was a problem hiding this comment.
Comments haven't been addressed
|
Added some tests for growing and shrinking tag ranges, as well as moving them between interfaces and links. |
Part of tests for kytos-ng/topology#281
Summary
Updates tests to properly use tag capable interfaces and links.
End-to-End Tests
Here are the results with all the tag_capable branches being used: