Updating Testing-Combo.md to reflect removed history functionality.

This commit is contained in:
Johannes Mockenhaupt 2017-12-07 23:23:37 +01:00
parent a38afe7a2a
commit 6e5f848c6b
No known key found for this signature in database
GPG key ID: 9E1EA6AF7BBBB0D1

View file

@ -3,25 +3,25 @@
- [ ] Bolusing
- [ ] Cancelling bolus at various stages and checking error message (if any) and check
no bolus or a partial bolus was delivered
- [ ] Cancelling a bolus 0.2 U before its finished (cancelling requires pressing up/down
- [ ] Cancelling a bolus 0.2 U before it's finished (cancelling requires pressing up/down
3s, so the cancellation will be too late, but the code should handle it and report
the full bolus being delivered
- [ ] Low cartridge alarm during bolus
- [ ] must be confirmed by AAPS
- [ ] alarm must be confirmed by AAPS
- [ ] bolus must have been fully delivered by pump
- [ ] bolus must have been added to DB
- [ ] the confirmed pump warning must be raised as a notification in AAPS
- [ ] notification must also appear on smartwatch
- [ ] An error during bolus must yield an error in AAPS
- [ ] An error during bolus must yield a notification on a smartwatch
- [ ] Bolusing e.g. 4 U if reservoir has only 2 U left must be rejected
- [ ] Bolusing e.g. 4 U if reservoir has only 2 U must yield a usable error
- [ ] Pressing a button on the pump before bolus delivery started must be handled gracefully
- [ ] Same as above, but moving pump out of range
- [ ] Pressing a button on the pump after bolus delivery has started must be handled
gracefully (bolus finished and AAPS must correctly add it the the DB)
- [ ] Same as above, but moving pump out of range
- [ ] Test the highest bolus you'd ever give yourself (AAPS has a configurable limit and the pump
has a limit which can be configured with the Config SW)
has a limit which can be configured with the Config SW), no timeout or other issues must show
- [ ] Test a bolus exceeding the pumps max bolus; should show a generic error message
- [ ] BT disconnect issues
- [ ] Moving pump out of reach when setting TBR causes "TBR cancelled" alarm on pump.
@ -30,9 +30,8 @@
- [ ] Same as above while bolusing must report an error and NOT retry the command
- [ ] AAPS start
- [ ] Starting AAPS without a reachable pump must show something sensible in the Combo tab
(that is not hang indefinitely with "initializing" activity)
- [ ] Starting AAPS without a reachable pump must trigger "pump unrechable" alert after
5 to 10 min.
(not hanging indefinitely with "initializing" activity)
- [ ] Starting AAPS without a reachable pump must trigger "pump unrechable" alert after the configured threshold
- [ ] If the pump's profile doesn't match AAPS', the pump must be updated when AAPS starts
- [ ] Doing a profile change (to shift time or increase/decrease insulin), the pump's basal profile must be updated
- [ ] If a profile change has a duration, the pump's basal profile must be set to the original value again at the end
@ -43,12 +42,14 @@
- [ ] Boluses
- [ ] TBR
- [ ] Alerts
- [ ] TDDs
- [ ] Disconnected pump (pump unreachable)
- [ ] ...
- [ ] With local alerts enabled for 'pump unreachable', an alert must be triggered within 5 minutes
after the configured threshold. (Don't set the threshold too low, e.g. 10 minutes, since
there might be no need to set a TBR within such a short time).
- [ ] Refilling cartridge
- [ ] If TBR was cancelled by refilling, AAPS must detect this and update the TBR treatment
accordingly
- [ ] If TBR was cancelled by refilling, AAPS must detect this and create a TBR record in AAPS
based on what the pump displays (not the full TBR duration, but what is displayed as remaining
on the main screen.
- [ ] Stress testing
- PersistentNotification plugin disabled
- Lots of comms running, like Wifi, GSM, BT audio
@ -58,22 +59,24 @@
- [ ] With the pump powered off or out of reach, the 'pump unreachable alert' must still
trigger
- [ ] Combo tab
- [ ] Check displayed data (state, battery, reservoir, last bolus, temp basal) is the same
- [ ] Check displayed data (state, battery, reservoir, bolus, temp basal) is the same
as on the pump
- [ ] Unsafe usage
- [ ] An extended or multiwave bolus given within the last six hour must raise an alert and
closed loop functionality (Loop plugin shows "disabled by constrains" when "execute" is pressed)
restrict the loop functionality to low-suspend only (setting maxIOB to zero)
- [ ] Closed loop functionality must resume 6 h after the last ext/multiwave bolus
- [ ] An active ext/multiwave bolus (a history record is created only after the bolus completed)
must also raise an alert and disable loop
must also raise an alert and restrict the loop
- [ ] If a basal rate other than profile 1 is activated, this must also raise an alert and disable
the loop for 6 h
the restrict the loop
- [ ] Reading/setting basal profile
- [ ] AAPS reads basal rate properly
- [ ] AAPS doesn't touch pump basal if "Sync to profile" pref not set
- [ ] AAPS updates basal rate if "Sync to profile" is enabled
- [ ] Test profile with 115% (or something like that) change to ask the
pump for basal rates like 0.812, which should then be set propely
- [ ] Updating the profile extensively (200%, shifting time) takes up to 6 minutes, but
should complete without timeout.
- [ ] Taking over alerts
- [ ] If an error alert is active on the pump, pressing refresh shall display the error
in the Combo tab but NOT confirm it. Easiest error to trigger: rewind piston