Skip to content
Snippets Groups Projects
Commit 31094e7a authored by Ozan Tanfener's avatar Ozan Tanfener
Browse files

Update testspec.md

parent 4f04ca83
Branches
Tags
1 merge request!10Questd network unit tests
# Test Specification
Most of the functionality in wifimngr can be tested via its ubus API. Each
Most of the functionality in questd can be tested via its ubus API. Each
API can be broken down into an individual test case to show full coverage is
achieved.
......@@ -8,34 +8,33 @@ achieved.
* [Preqreuisites](#prerequisites)
* [Test Suites](#test-suites)
* [Functional API Tests](#functional-api-tests)
* [Unit Tests](#unit-tests)
* [Functional Tests](#functional-tests)
* [Writing New Tests](#writing-new-tests)
## Prerequisites
The only prerequisite for the wifimngr test suites is that libwifi has to be
built for the TEST platform, a versionprepared to publish dummy data for getter
API, and record setter API to a test logfile at `/tmp/test.log`.
Prerequisites for the questd test suites can be listed as follows:
* Docker container have to run with NET_ADMIN capability because various network parameters must be configured.
* wifimngr has to be built for the TEST platform due to the internal usage
* bridge-utils must be installed in order to do necessary bridge configurations that is required for questd.
## Test Suites
The wifimngr build pipe has three test suites, a functional-api suite, a unit
testi suite and functional test suite.
The questd build pipe has two test suites, a functional-api suite,and a functional test suite.
### Functional API Tests
The functional API tests consists of four individual test suites, one per object
The functional API tests consists of one individual test suites, one per object
Ubus under test. The functional API tests use the Ubus-API-validation
command-line interface tool to invoke a method, programmatically through
libubus, and validates it against the objects json-schema.
#### wifi
#### network
| Execution ID | Method | Description | Function ID Coverage |
| :--- | :--- | :--- | :--- |
| 1 | status | No argument | [1](./functionspec.md#status) |
| 1 | hosts | No argument | [1](./functionspec.md#hosts) |
| 2 | dummy | Negative Test | |
#### wifi.ap.\<name\>
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment