Unit Tests to Check Conformance to API Spec
The goal is to make sure that any requirement stated in the API spec is checked by an associated unit test (e.g., that a tenant may not have two networks of the same name). We can then create a unit test infrastructure that loads each plugin and runs this test for it.
Proposed plan for the implementation of this blueprint:
- distinct modules will be defined for each functional area of the source code tree. We will start with api, db, cli, and utils
- for each operation the following unit tests should be provided:
A) success unit test
B) failure unit tests for expected faults (e.g.: Network in use for the API)
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- Salvatore Orlando
- Direction:
- Needs approval
- Assignee:
- Salvatore Orlando
- Definition:
- New
- Series goal:
- None
- Implementation:
- Implemented
- Milestone target:
- diablo-4
- Started by
- Salvatore Orlando
- Completed by
- Salvatore Orlando
Whiteboard
Salvatore (29/06) - Linking branch owned by ~netstack for Collaborative Development
Salvatore (01/07) - Starting to populate unit tests.
Salvatore (04/07) - Adapted plugin interface to accept options from API layer, in order to drive fake plugin class and fake db name from tests
Salvatore (05/07) - Now using in-memory sqllite db. Populating unit tests for API.