Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Q
questd
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Issue analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
IOPSYS
questd
Commits
31094e7a
Commit
31094e7a
authored
4 years ago
by
Ozan Tanfener
Browse files
Options
Downloads
Patches
Plain Diff
Update testspec.md
parent
4f04ca83
Branches
Branches containing commit
Tags
Tags containing commit
1 merge request
!10
Questd network unit tests
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/testspec.md
+9
-10
9 additions, 10 deletions
docs/testspec.md
with
9 additions
and
10 deletions
docs/testspec.md
+
9
−
10
View file @
31094e7a
# 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 | st
atu
s | No argument |
[
1
](
./functionspec.md#st
atu
s
)
|
| 1 |
ho
sts | No argument |
[
1
](
./functionspec.md#
ho
sts
)
|
| 2 | dummy | Negative Test | |
#### wifi.ap.\<name\>
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment