/
Async job processing test cases

ЕСОЗ - публічна документація

Async job processing test cases

Owned by Petro Lymych (Unlicensed)
Last updated: Feb 22, 2019 by Iryna Biiovska
n/n
Description
Inputs
expected result
actual  result
Status
1Create pkg - success
  1. system operates normally
  2. POST proper pkg data that should pass all the validations
  1. job.data.status: "processed"
  2. job.data.status_code: "200"
  3. links to all created entities returned in job details
  4. GET job.code: 303

passed
2Create pkg - failed validation
  1. system operates normally
  2. POST proper pkg data that shouldn't pass some validation
  1. job.data.status: "error"
  2. job.data.status_code: "422"
  3. GET job.code: 200

passed
3Create pkg, one IL pod is down
  1. one IL pod is down
  2. POST proper pkg data that should pass all the validations
  1. job.data.status: "processed"
  2. job.data.status_code: "200"
  3. links to all created entities returned in job details
  4. GET job.code: 303

passed
4Create pkg, all IL pods are down
  1. all IL pod is down
  2. POST proper pkg data that should pass all the validations
  1. job.data.status: "failed_with_error"
  2. job.data.status_code: "500"
  3. GET job.code: 200

passed
5Create pkg, MongoDB is down
  1. mongoBD is down
  2. POST proper pkg data that should pass all the validations
500No response
http_code: 500
Timeout: 60106 ms		?
6Create pkg, failed to insert to Observations collection
  1. mongoBD is up
  2. failed to insert into Observations collection
  3. POST proper pkg data that should pass all the validations
A:
  1. job.data.status: "pending"
  2. job.data.status_code: "202"
  3. GET job.code: 200

B: after observations is up

  1. job.data.status: "processed"
  2. job.data.status_code: "200"
  3. links to all created entities returned in job details
  4. GET job.code: 303


Cant be reproduced


  1. Even Consumer is down, MongoBD is up
  2. Job created
  3. Even Consumer is down, MongoBD is down
  4. Even Consumer is up, MongoBD is up
  1. job.data.status: "processed"
  2. job.data.status_code: "200"
  3. links to all created entities returned in job details
  4. GET job.code: 303
"errors": "Aborting transaction. connection(me-db-mongodb-replicaset-0.me-db-mongodb-replicaset.me-db.svc.cluster.local:27017[-431]) unable to decode message length: EOF",
"eta": "2019-02-21T09:55:11.445",
"status": "failed",
"status_code": 500		Can not reproduce again
7Create pkg, failed to update job status
  1. mongoBD is up
  2. POST proper pkg data that should pass all the validations
  3. all the objects has been successfully updated/inserted
  4. failed to update job status
A:
  1. job.data.status: "pending"
  2. job.data.status_code: "202"
  3. GET job.code: 200

B: after jobs collection is up

  1. job.data.status: "processed"
  2. job.data.status_code: "200"
  3. links to all created entities returned in job details
  4. GET job.code: 303




8Create pkg, one DS service pod is down
  1. one DS service is down
  2. POST proper pkg data that should pass all the validations

ASIS:

  1. job.data.status: "failed_with_error"
  2. job.data.status_code: "500"
  3. GET job.code: 200

TOBE:

  1. job.data.status: "processed"
  2. job.data.status_code: "200"
  3. links to all created entities returned in job details
  4. GET job.code: 303
  1. job.data.status: "processed"
  2. job.data.status_code: "200"
  3. links to all created entities returned in job details
  4. GET job.code: 303
passed
9Create pkg, all DS service pods are down
  1. job.data.status: "failed_with_error"
  2. job.data.status_code: "500"
  3. GET job.code: 200
"errors": "%Core.Microservices.Error{message: :connect_timeout}",
"eta": "2019-02-21T10:16:01.602",
"status": "failed_with_error",
"status_code": 500		passed
10Create pkg, kafka is down
  1. kafka is down
  2. POST proper pkg data that should pass all the validations
500{
"error": {
"type": "internal_error"
},
"meta": {
"code": 500,
"request_id": "a39037e0-7829-4acb-8634-cf02f1b31793#2167",
"type": "object",
"url": "http://api-medical-events.me.svc.cluster.local/api/patients/7d60d862-6df2-4dd9-95b3-7496b189b906/encounter_package"
}
}		passed
11Create pkg, ael service is down
  1. ael is down
  2. POST proper pkg data that should pass all the validations
  1. job.data.status: "failed_with_error"
  2. job.data.status_code: "500"
  3. GET job.code: 200
"errors": "%Core.Microservices.Error{message: :connect_timeout}",
"eta": "2019-02-21T10:19:08.554",
"status": "failed_with_error",
"status_code": 500		passed
12Get data when IL is down
?always 403
13Transaction
  1. Send 2 packages with the same condition.id in short period of time(ms)
Validations passed
First package created
Second package failed with 500
Nothing was created from the second package 		Validations passed
First package created
Second package failed with 500
Nothing was created from the second package		passed

Related content

ME async job processing
ME async job processing
E-Health
More like this
Medical events Technical Documentation
Medical events Technical Documentation
E-Health
More like this
Створення або зміна ідентифікованої персони
Створення або зміна ідентифікованої персони
E-Health
Read with this
Jabba service
Jabba service
E-Health
More like this
E-Health UI Design
E-Health UI Design
E-Health
Read with this
Get async Job processing details
Get async Job processing details
E-Health
More like this

ЕСОЗ - публічна документація