Test Coverage

The intention is to track merged features or areas of code that lack certain types of tests. This document may be used both by developers that want to contribute tests, and operators that are considering adopting a feature.

Coverage

Note that while both API and scenario tests target a deployed OpenStack cloud, API tests are under the Neutron tree and scenario tests are under the Tempest tree.

It is the expectation that API changes involve API tests, agent features or modifications involve functional tests, and Neutron-wide features involve fullstack or scenario tests as appropriate.

The table references tests that explicitly target a feature, and not a job that is configured to run against a specific backend (Thereby testing it implicitly). So, for example, while the Linux bridge agent has a job that runs the API and scenario tests with the Linux bridge agent configured, it does not have functional tests that target the agent explicitly. The ‘gate’ column is about running API/scenario tests with Neutron configured in a certain way, such as what L2 agent to use or what type of routers to create.

• V - Merged
• Blank - Not applicable
• X - Absent or lacking
• Patch number - Currently in review
• A name - That person has committed to work on an item
• Implicit - The code is executed, yet no assertions are made

Area	Unit	Functional	API	Fullstack	Scenario	Gate
DVR	V	L3-V OVS-X	V	X	X	V
L3 HA	V	V	X	286087	X	X
L2pop	V	X		Implicit
DHCP HA	V			amuller
OVS ARP responder	V	X*		X*
OVS agent	V	V		V		V
Linux Bridge agent	V	X		V		V
Metering	V	X	V	X
DHCP agent	V	V		amuller		V
rpc_workers						X
Reference ipam driver	V					X
MTU advertisement	V			X
VLAN transparency	V		X	X
Prefix delegation	V	X		X

• Prefix delegation doesn’t have functional tests for the dibbler and pd layers, nor for the L3 agent changes. This has been an area of repeated regressions.
• The functional job now compiles OVS 2.5 from source, enabling testing features that we previously could not. The OVS ARP responder is one such feature. Modifying the fullstack job to use OVS 2.5 as well will enable testing the OVS ARP responder implicitly.

Missing Infrastructure

The following section details missing test types. If you want to pick up an action item, please contact amuller for more context and guidance.

• The Neutron team would like Rally to persist results over a window of time, graph and visualize this data, so that reviewers could compare average runs against a proposed patch.
• It’s possible to test RPC methods via the unit tests infrastructure. This was proposed in patch 162811. The goal is provide developers a light weight way to rapidly run tests that target the RPC layer, so that a patch that modifies an RPC method’s signature could be verified quickly and locally.
• Neutron currently runs a ‘partial-grenade’ job that verifies that an OVS version from the latest stable release works with neutron-server from master. We would like to expand this to DHCP and L3 agents as well.