Support #2427
Exception situations tests
0%
Description
Test the system behavior on situations bellow:
- Exception during client init
- Exception during server / client sync
- Change user unit (server side)
- Case transference (check if case will still appear on client side)
History
#1
Updated by Maurício Dos Santos over 8 years ago
- Check ia a offline instance can start treat of a case in another treatment unit.
#2
Updated by Maurício Dos Santos over 8 years ago
- Status changed from New to In Progress
#3
Updated by Maurício Dos Santos over 8 years ago
- Status changed from In Progress to Feedback
- Assignee changed from Maurício Dos Santos to Ricardo Memoria
- Exception during client init
- Exception during server / client sync
All expected exceptions are being treated. Any unexpected exception will block client side until restarting it.
- Change user unit (server side)
Not possible to test, server has a bug on user form that doesn't allow to change user view.
- Case transference (check if case will still appear on client side)
Expected behavior. All cases related to a unit (owner unit, treatment health unit, tranfer out unit or notification unit) will be on the client side database.
- Check ia a offline instance can start treat of a case in another treatment unit.
It could, but the system was modified to block it.
#4
Updated by Maurício Dos Santos over 8 years ago
- Status changed from Feedback to In Progress
#5
Updated by Maurício Dos Santos over 8 years ago
- Exception during client init
- Exception during server / client sync
All expected exceptions are being treated. Any unexpected exception will block client side until restarting it. Need to change it.
- Change user unit (server side)
The user unit on client side will not be updated because of the ServerTableQueryList conditions. As the user is now from another unit, the userworkspace on ServerTableQueryList will not selecte the modified user. So the modified user continues to have access to the previous unit.
Should it continue like this?
#6
Updated by Maurício Dos Santos over 8 years ago
- Exception during client init
- Exception during server / client sync
All expected exceptions are being treated. Any unexpected exception will block client side until restarting it. Need to change it.
- Change user unit (server side)
The user unit on client side will not be updated because of the ServerTableQueryList conditions. As the user is now from another unit, the userworkspace on ServerTableQueryList will not selecte the modified user. So the modified user continues to have access to the previous unit.
Should it continue like this?
- Case Transference
As the patient table is not modified when a case is transfered, its version is not updated, so when tranfering the case is sent to the new unit but not its patient, causing a relation exception
#7
Updated by Maurício Dos Santos over 8 years ago
- Exception during client init
- Exception during server / client sync
Resolved. An error message will appear and phase will be cleared on service, so it will not follow blocked.
Still pending:
- Change user unit (server side)
The user unit on client side will not be updated because of the ServerTableQueryList conditions. As the user is now from another unit, the userworkspace on ServerTableQueryList will not selecte the modified user. So the modified user continues to have access to the previous unit.
Should it continue like this?
- Case Transference
As the patient table is not modified when a case is transfered, its version is not updated, so when tranfering the case is sent to the new unit but not its patient, causing a relation exception
#8
Updated by Maurício Dos Santos over 8 years ago
- Status changed from In Progress to Resolved
Decided to let it as todo issues.
#9
Updated by Ricardo Memoria over 8 years ago
- Status changed from Resolved to Closed