Skip to content

Commit

Permalink
doc: smoke test on upgrade
Browse files Browse the repository at this point in the history
  • Loading branch information
vokimon committed Nov 26, 2021
1 parent 854a79f commit 5b7014b
Showing 1 changed file with 15 additions and 0 deletions.
15 changes: 15 additions & 0 deletions doc/development.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,21 @@ pip install -e .
sudo supervisorctl restart tomatic
```

## Smoke tests

(Som Energia specific, you could adapt them)

What smoke tests you should be doing after an upgrade to check most components should be up and running:

- Go to http://tomatic.somenergia.lan and check it shows the production pbx queue, modify the queue (ie, add yourself and pause)
- Go to http://ketchup.somenergia.lan and check it works the testing pbx queue, should be different than production, modify it
- Go to http://tomatic.somenergia.lan:500 and check scriptlauncher, use an script, ie, reset the queue, to reset former changes to the queues
- Check tomatic says from scriptlauncher with you email as a target (certificates and api versions problems might trigger)
- Login as one of the operators and check callinfo shows the former calls, click one that triggers a search
- Go to the scriptlauncher and launch a shift load (will trigger any problems on downloading required data: odoo, drive connections...)
- Go to the planner and launch a timetable (will trigger any problems on downloading required data: odoo, drive connections...). Delete the task to avoid messing AiS team.
- As root (to keep userid and perms), uncomment the testing crontab line to check crontab is fine and working

## Code map

### API
Expand Down

0 comments on commit 5b7014b

Please sign in to comment.