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

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 6 Next »

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
500

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




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


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


10Create pkg, kafka is down
  1. kafka is down
  2. POST proper pkg data that should pass all the validations
500

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


12Get data when IL is down
?always 403
  • No labels

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