mirror of
https://github.com/gurucomputing/headscale-ui.git
synced 2026-01-23 02:34:43 +00:00
update test documentation
This commit is contained in:
parent
cba8d7df68
commit
107b012098
6 changed files with 37 additions and 3 deletions
|
|
@ -76,10 +76,10 @@ hs.yourdomain.com.au {
|
|||
```
|
||||
|
||||
## Development
|
||||
see [development](/documentation/Development.md) for details
|
||||
see [development](/documentation/development.md) for details
|
||||
|
||||
### Style Guide
|
||||
see [style](/documentation/Style.md) for details
|
||||
see [style](/documentation/style.md) for details
|
||||
|
||||
## Architecture
|
||||
See [architecture](/documentation/Architecture.md) for details
|
||||
See [architecture](/documentation/architecture.md) for details
|
||||
|
|
|
|||
|
|
@ -2,6 +2,10 @@
|
|||
|
||||
Development can be done either by using the official development docker image, or via a normal nodejs installation.
|
||||
|
||||
## Testing
|
||||
|
||||
All branches should undergo manual testing as specified in the [System Integration Testing](./system-integration-testing.md) document. If someone is well versed in unit automation tests for browser front ends, please educate me! For now do it manually before making a pull request.
|
||||
|
||||
### Quick Start (Docker)
|
||||
* `docker run -p 443:443 -p 3000:3000 -v "$(pwd)"/data:/data ghcr.io/gurucomputing/headscale-ui-dev:latest`
|
||||
|
||||
30
documentation/system-integration-testing.md
Normal file
30
documentation/system-integration-testing.md
Normal file
|
|
@ -0,0 +1,30 @@
|
|||
## Tests Before Release
|
||||
Eventually it would be nice to automate this, but I've found a front end is difficult to fully automate testing. Prove me wrong other users!
|
||||
|
||||
## User Testing
|
||||
* Create a User
|
||||
* Delete a User
|
||||
* Rename a User
|
||||
* Create a PreAuth Key
|
||||
* Try all Sort Categories
|
||||
|
||||
## Device Testing
|
||||
* Add a Device with a Preauth Key
|
||||
* Add a Device with a machine key
|
||||
* Add a Device with OIDC (if set up to do so)
|
||||
* Rename a Device
|
||||
* Try all sort categories
|
||||
* Create a Tag
|
||||
* Delete a Tag
|
||||
* Delete a Device
|
||||
* Add and approve a route (if set up to do so)
|
||||
* Change the assigned user for a device
|
||||
|
||||
## Failure Test
|
||||
* Test messages (both console and alerts) with failed apikey
|
||||
* Test recovery once apikey is back
|
||||
* Test messages (both console and alerts) with failed URL
|
||||
* Test recovery once URL is back
|
||||
|
||||
## Settings Test
|
||||
* Verify version comes across once released
|
||||
Loading…
Add table
Add a link
Reference in a new issue