Unit Tests

Table of contents:

• Coverage
• Testing scenarios
• Unit tests

Coverage

branch	coverage
master
pantheon-dev
dev

Testing scenarios

Theses tests basically test whole agent while mocking all external services (ETCD, VPP, etc.). This means they should be called from northbound API and then check that various related plugins act as expected.

• memif suite
  • add/delete interface
• ifplugin/l2plugin integration
  • add/remove bridge domain with interfaces
  • add/remove interfaces to/from existing bridge domain
  • add interface, bridge domain and FIB entry (also in reversed order)
  • configure FIB entry, then remove interface
• ifplugin/l3plugin integration
  • add interface and arp entry (also in reversed order)
  • add interface and route (also in reversed order)
• ifplugin resync
  • add interfaces of every type, restart agent & vpp
  • add interfaces of every type, restart agent only
  • add/remove interfaces while agent is off with empty VPP
  • add/remove interfaces while agent is off with configured VPP
  • start agent with unknown interface on VPP (ETCD config does not exist)

Unit tests

These tests should test functionality at the package level.

• ifplugin
  • ...
• l2plugin
  • ...
  • bdidx
    • index metadata
    • register/unregister name
    • lookup index
    • lookup name
    • lookup by iface name
• l3plugin
  • ...
• l4plugin
  • ...