Continuous Tests

This page outlines the success and failure criteria for all tests of Continuous resources.

Continuous API Tests

Continuous API tests assert the correct configuration of continuous-related API routes. In order for a test case to succeed, the following conditions must be met when evaluating the response:

  • For all cases, Content-Type checking is enforced. For most routes, a value of application/vnd.ga4gh.rnaget.v1.0.0+json OR application/json is expected. For the /continuous/<id> endpoint, a content type matching the format of the file attachment is expected.

  • For all cases, Status Code checking is enforced. The response MUST have the expected status code

  • For all cases, schema checking is enforced. The json object in the response body MUST conform to a pre-defined schema of required fields and data types, which is specific to each API route

Continuous API Test Cases

Get Supported Continuous Formats

  • Route: /continuous/formats

  • Description: Requests the available continuous file formats on the server. Expects an array of strings to be returned in the response body.

  • Rationale: Asserts that /continuous/formats returns an array of strings, indicating which continuous file formats the server supports

  • Request:

GET /continuous/formats
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Successful Response:

HTTP/1.1 200 OK
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

[
  "loom",
  "tsv"
]

  • Success Criteria: Status Code == 200 AND response body is an array of strings in json format

  • Failure Criteria: Status Code != 200 OR response body is NOT an array of strings in json format

Continuous Filters

  • Route: /continuous/filters

  • Description: Requests the filters that can be used to narrow search results for a list of Continuous

  • Rationale: Asserts that the endpoint returns an array of filters

  • Request:

GET /continuous/filters
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Successful Response:

HTTP/1.1 200 OK
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

[
  {
    "fieldType": "string",
    "values": [
      "1.0"
    ],
    "filter": "version",
    "description": "version to search for"
  },
  {
    "fieldType": "string",
    "filter": "studyID",
    "description": "parent studyID"
  }
]

  • Success Criteria: Status Code == 200 AND response body is array of filters

  • Failure Criteria: Status Code != 200 OR response body is NOT array of filters

Get Test Continuous Ticket

  • Route: /continuous/<id>/ticket

  • Description: Requests continuous ticket by its id. Expects valid ticket.

  • Rationale: Asserts that /continuous/<id>/ticket returns valid ticket.

  • Request:

GET /continuous/5e22e009f41fc53cbea094a41de8798f/ticket
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Successful Response:

HTTP/1.1 200 OK
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

{
  "id": "5e22e009f41fc53cbea094a41de8798f",
  "version": "1.0",
  "studyID": "f3ba0b59bed0fa2f1030e7cb508324d1",
  "url": "https://url/to/continuous/file",
  "units": "TPM",
  "fileType": "loom/tsv"
}

  • Success Criteria: Status Code == 200 AND response is ticket

  • Failure Criteria: Status Code != 200 OR response is NOT ticket

Single Continuous Ticket - Not Found

  • Route: /continuous/<id>/ticket

  • Description: Requests continuous ticket with an invalid id. Expects a 404 Not Found status code in the response, and error message.

  • Rationale: Asserts that the /continuous/<id>/ticket endpoint does not return arbitrary ticket.

  • Request:

GET /continuous/nonexistentid9999999999999999999/ticket
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Successful Response:

HTTP/1.1 404 Not Found
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

{
  "message": "Entry not found in database."
}

  • Success Criteria: Status Code == 404 AND response body is valid Error json

  • Failure Criteria: Status Code != 404 OR response body is NOT valid Error json

Single Continuous Ticket - Start Specified Without Chr

  • Route: /continuous/<id>/ticket

  • Description: Requests continuous ticket by its id, specifying a start position without a chromosome. Expects a 400 Bad Request status code in the response, and an error message

  • Rationale: Asserts that the /continuous/<id>/ticket endpoint raises an error when start is specified without chr

  • Request:

GET /continuous/5e22e009f41fc53cbea094a41de8798f/ticket?start=5
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Successful Response:

HTTP/1.1 400 Bad Request
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

{
  "message": "chr required if either start or end is specified"
}

  • Success Criteria: Status Code == 400 AND response body is valid Error json

  • Failure Criteria: Status Code != 400 OR response body is NOT valid Error json

Single Continuous Ticket - End Specified Without Chr

  • Route: /continuous/<id>/ticket

  • Description: Requests test continuous by its id, specifying an end position without a chromosome. Expects a 400 Bad Request status code in the response, and an error message

  • Rationale: Asserts that the /continuous/<id>/ticket endpoint raises an error when end is specified without chr

  • Request:

GET /continuous/5e22e009f41fc53cbea094a41de8798f/ticket?end=1000
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Successful Response:

HTTP/1.1 400 Bad Request
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

{
  "message": "chr required if either start or end is specified"
}

  • Success Criteria: Status Code == 400 AND response body is valid Error json

  • Failure Criteria: Status Code != 400 OR response body is NOT valid Error json

Single Continuous Ticket - Start Greater Than End

  • Route: /continuous/<id>/ticket

  • Description: Requests test continuous ticket by its id, specifying chr, start, and end, however, start position is greater than end. Expects a 400 Bad Request status code in the response, and an error message

  • Rationale: Asserts that the /continuous/<id>/ticket endpoint raises an error when start is greater than end

  • Request:

GET /continuous/5e22e009f41fc53cbea094a41de8798f/ticket?chr=1&start=200&end=100
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Successful Response:

HTTP/1.1 400 Bad Request
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

{
  "message": "start cannot be greater than end"
}

  • Success Criteria: Status Code == 400 AND response body is valid Error json

  • Failure Criteria: Status Code != 400 OR response body is NOT valid Error json

Get Test Continuous Bytes

  • Route: /continuous/<id>/bytes

  • Description: Requests continuous matrix bytes by its id.

  • Rationale: Asserts that /continuous/<id>/bytes returns matrix bytes.

  • Request:

GET /continuous/5e22e009f41fc53cbea094a41de8798f/bytes
Accept: application/octet-stream, application/vnd.loom, text/tab-separated-values

  • Successful Response:

HTTP/1.1 200 OK
Content-Type: application/octet-stream

  • Success Criteria: Status Code == 200

  • Failure Criteria: Status Code != 200

Single Continuous Bytes - Not Found

  • Route: /continuous/<id>/bytes

  • Description: Requests continuous bytes with an invalid id. Expects a 404 Not Found status code in the response, and error message.

  • Rationale: Asserts that the /continuous/<id>/bytes endpoint does not return arbitrary matrix.

  • Request:

GET /continuous/nonexistentid9999999999999999999/bytes
Accept: application/octet-stream, application/vnd.loom, text/tab-separated-values

  • Successful Response:

HTTP/1.1 404 Not Found
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

{
  "message": "Entry not found in database."
}

  • Success Criteria: Status Code == 404 AND response body is valid Error json

  • Failure Criteria: Status Code != 404 OR response body is NOT valid Error json

Single Continuous Bytes - Start Specified Without Chr

  • Route: /continuous/<id>/bytes

  • Description: Requests continuous matrix bytes by its id, specifying a start position without a chromosome. Expects a 400 Bad Request status code in the response, and an error message

  • Rationale: Asserts that the /continuous/<id>/bytes endpoint raises an error when start is specified without chr

  • Request:

GET /continuous/5e22e009f41fc53cbea094a41de8798f/bytes?start=5
Accept: application/octet-stream, application/vnd.loom, text/tab-separated-values

  • Successful Response:

HTTP/1.1 400 Bad Request
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

{
  "message": "chr required if either start or end is specified"
}

  • Success Criteria: Status Code == 400 AND response body is valid Error json

  • Failure Criteria: Status Code != 400 OR response body is NOT valid Error json

Single Continuous Bytes - End Specified Without Chr

  • Route: /continuous/<id>/bytes

  • Description: Requests test continuous matrix bytes by its id, specifying an end position without a chromosome. Expects a 400 Bad Request status code in the response, and an error message

  • Rationale: Asserts that the /continuous/<id>/bytes endpoint raises an error when end is specified without chr

  • Request:

GET /continuous/5e22e009f41fc53cbea094a41de8798f/bytes?end=1000
Accept: application/octet-stream, application/vnd.loom, text/tab-separated-values

  • Successful Response:

HTTP/1.1 400 Bad Request
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

{
  "message": "chr required if either start or end is specified"
}

  • Success Criteria: Status Code == 400 AND response body is valid Error json

  • Failure Criteria: Status Code != 400 OR response body is NOT valid Error json

Single Continuous Bytes - Start Greater Than End

  • Route: /continuous/<id>/bytes

  • Description: Requests test continuous matrix bytes by its id, specifying chr, start, and end, however, start position is greater than end. Expects a 400 Bad Request status code in the response, and an error message

  • Rationale: Asserts that the /continuous/<id>/bytes endpoint raises an error when start is greater than end

  • Request:

GET /continuous/5e22e009f41fc53cbea094a41de8798f/bytes?chr=1&start=200&end=100
Accept: application/octet-stream, application/vnd.loom, text/tab-separated-values

  • Successful Response:

HTTP/1.1 400 Bad Request
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

{
  "message": "start cannot be greater than end"
}

  • Success Criteria: Status Code == 400 AND response body is valid Error json

  • Failure Criteria: Status Code != 400 OR response body is NOT valid Error json

Continuous Ticket by Format

  • Route: /continuous/ticket

  • Description: Requests joined continuous matrix, specifying only the required ‘format’ parameter. Expects ticket.

  • Rationale: Asserts that /continuous/ticket returns a ticket with which the matrix can be downloaded.

  • Request:

GET /continuous/ticket?format=loom
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Successful Response:

HTTP/1.1 200 OK
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

{
  "studyID": "6cccbbd76b9c4837bd7342dd616d0fec",
  "url": "/path/to/signal-query-results.loom",
  "units": "TPM",
  "version": "1.0",
  "fileType": "loom"
}

  • Success Criteria: Status Code == 200 AND response body is ticket

  • Failure Criteria: Status Code != 200 OR response body is NOT ticket

Continuous Ticket - All Filters

  • Route: /continuous/ticket

  • Description: Requests joined continuous matrix, using all filtering parameters. Expects ticket.

  • Rationale: Asserts that /continuous/ticket returns ticket when specifying filters.

  • Request:

GET /continuous/ticket?format=loom&version=1.0&studyID=f3ba0b59bed0fa2f1030e7cb508324d1
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Successful Response:

HTTP/1.1 200 OK
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

{
  "studyID": "f3ba0b59bed0fa2f1030e7cb508324d1",
  "url": "/path/to/continuous.loom",
  "units": "TPM",
  "version": "1.0",
  "fileType": "loom"
}

  • Success Criteria: Status Code == 200 AND response body is ticket

  • Failure Criteria: Status Code != 200 OR response body is NOT ticket

Continuous Ticket - Single Filter, 1

  • Route: /continuous/ticket

  • Description: Requests joined continuous matrix, using only 1 filtering parameter associated with test continuous (in addition to format). Expects ticket.

  • Rationale: Asserts filtering parameters can be used independently of one another, and that each filter yields a valid ticket.

  • Requests:

GET /continuous/ticket?format=loom&version=1.0
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Successful Response:

HTTP/1.1 200 OK
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

{
  "url": "/path/to/signal-query-results.loom",
  "units": "TPM",
  "version": "1.0",
  "fileType": "loom"
}

  • Success Criteria: Status Code == 200 AND response body is ticket.

  • Failure Criteria: Status Code != 200 OR response body is NOT ticket.

Continuous Ticket - Single Filter, 2

  • Route: /continuous/ticket

  • Description: Requests joined continuous matrix, using only 1 filtering parameter (different than above) associated with test continuous (in addition to format). Expects ticket.

  • Rationale: Asserts filtering parameters can be used independently of one another, and that each filter yields a valid ticket.

  • Requests:

GET /continuous/ticket?format=loom&studyID=f3ba0b59bed0fa2f1030e7cb508324d1
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Successful Response:

HTTP/1.1 200 OK
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

{
  "studyID": "6cccbbd76b9c4837bd7342dd616d0fec",
  "url": "/path/to/signal-query-results.loom",
  "units": "TPM",
  "fileType": "loom"
}

  • Success Criteria: Status Code == 200 AND response body is ticket.

  • Failure Criteria: Status Code != 200 OR response body is NOT ticket.

Continuous Ticket - Format Not Specified

  • Route: /continuous/ticket

  • Description: Requests joined continuous matrix WITHOUT specifying the required format parameter. Expects a 4xx response with error message.

  • Rationale: As the format parameter is required to specify file format for the /continuous/ticket endpoint, this test asserts malformed requests raise an error.

  • Request:

GET /continuous/ticket
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Successful Response:

HTTP/1.1 400 Bad Request
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

{
  "message": "Input payload validation failed"
}

  • Success Criteria: Status Code == 4xx AND response body is valid Error json

  • Failure Criteria: Status Code != 4xx AND response body is NOT valid Error json

Continuous Ticket - Filetype Matches

  • Route: /continuous/ticket

  • Description: Request joined continuous matrix, only specifying the required format parameter. Checks that ticket has a fileType matching requested format.

  • Rationale: Asserts that the /continuous/ticket endpoint returns ticket with fileType matching the request.

  • Request:

GET /continuous/ticket?format=loom
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Successful Response:

HTTP/1.1 200 OK
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

{
  "studyID": "6cccbbd76b9c4837bd7342dd616d0fec",
  "url": "/woldlab/castor/home/sau/public_html/rnaget/signal-query-results.loom",
  "units": "TPM",
  "version": "1.0",
  "fileType": "loom"
}

  • Success Criteria: Status Code == 200 AND response body is ticket AND fileType matches requested format

  • Failure Criteria: Status Code != 200 OR response body is NOT ticket OR fileType DOES NOT match requested format

Continuous Ticket - Start Specified Without Chr

  • Route: /continuous/ticket

  • Description: Requests joined continuous matrix ticket, specifying a start position without a chromosome. Expects a 400 Bad Request status code in the response, and an error message

  • Rationale: Asserts that the /continuous/ticket endpoint raises an error when start is specified without chr

  • Request:

GET /continuous/ticket?format=loom&start=5
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Successful Response:

HTTP/1.1 400 Bad Request
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

{
  "message": "chr required if either start or end is specified"
}

  • Success Criteria: Status Code == 400 AND response body is valid Error json

  • Failure Criteria: Status Code != 400 OR response body is NOT valid Error json

Continuous Ticket - End Specified Without Chr

  • Route: /continuous/ticket

  • Description: Requests joined continuous matrix ticket, specifying an end position without a chromosome. Expects a 400 Bad Request status code in the response, and an error message

  • Rationale: Asserts that the /continuous/ticket endpoint raises an error when end is specified without chr

  • Request:

GET /continuous/ticket?format=loom&end=1000
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Successful Response:

HTTP/1.1 400 Bad Request
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

{
  "message": "chr required if either start or end is specified"
}

  • Success Criteria: Status Code == 400 AND response body is valid Error json

  • Failure Criteria: Status Code != 400 OR response body is NOT valid Error json

Continuous Ticket - Start Greater Than End

  • Route: /continuous/ticket

  • Description: Requests joined continuous matrix ticket, specifying chr, start, and end, however, start position is greater than end. Expects a 400 Bad Request status code in the response, and an error message

  • Rationale: Asserts that the /continuous/ticket endpoint raises an error when start is greater than end

  • Request:

GET /continuous/ticket?format=loom&chr=1&start=200&end=100
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Successful Response:

HTTP/1.1 400 Bad Request
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

{
  "message": "start cannot be greater than end"
}

  • Success Criteria: Status Code == 400 AND response body is valid Error json

  • Failure Criteria: Status Code != 400 OR response body is NOT valid Error json

Continuous Bytes by Format

  • Route: /continuous/bytes

  • Description: Requests joined continuous matrix as bytes, specifying only the required ‘format’ parameter.

  • Rationale: Asserts that /continuous/bytes returns matrix bytes.

  • Request:

GET /continuous/bytes?format=loom
Accept: application/octet-stream, application/vnd.loom, text/tab-separated-values

  • Successful Response:

HTTP/1.1 200 OK
Content-Type: application/octet-stream

  • Success Criteria: Status Code == 200

  • Failure Criteria: Status Code != 200

Continuous Bytes - All Filters

  • Route: /continuous/bytes

  • Description: Requests joined continuous matrix as bytes, using all filtering parameters.

  • Rationale: Asserts that /continuous/ticket returns matrix bytes when specifying filters.

  • Request:

GET /continuous/bytes?format=loom&version=1.0&studyID=f3ba0b59bed0fa2f1030e7cb508324d1
Accept: application/octet-stream, application/vnd.loom, text/tab-separated-values

  • Successful Response:

HTTP/1.1 200 OK
Content-Type: application/octet-stream

  • Success Criteria: Status Code == 200

  • Failure Criteria: Status Code != 200

Continuous Bytes - Single Filter, 1

  • Route: /continuous/bytes

  • Description: Requests joined continuous matrix as bytes, using only 1 filtering parameter associated with test continuous (in addition to format).

  • Rationale: Asserts filtering parameters can be used independently of one another.

  • Requests:

GET /continuous/bytes?format=loom&version=1.0
Accept: application/octet-stream, application/vnd.loom, text/tab-separated-values

  • Successful Response:

HTTP/1.1 200 OK
Content-Type: application/octet-stream

  • Success Criteria: Status Code == 200

  • Failure Criteria: Status Code != 200

Continuous Bytes - Single Filter, 2

  • Route: /continuous/bytes

  • Description: Requests joined continuous matrix as bytes, using only 1 filtering parameter (different than above) associated with test continuous (in addition to format).

  • Rationale: Asserts filtering parameters can be used independently of one another.

  • Requests:

GET /continuous/bytes?format=loom&studyID=f3ba0b59bed0fa2f1030e7cb508324d1
Accept: application/octet-stream, application/vnd.loom, text/tab-separated-values

  • Successful Response:

HTTP/1.1 200 OK
Content-Type: application/octet-stream

  • Success Criteria: Status Code == 200

  • Failure Criteria: Status Code != 200

Continuous Bytes - Format Not Specified

  • Route: /continuous/bytes

  • Description: Requests joined continuous matrix as bytes WITHOUT specifying the required format parameter. Expects a 4xx response with error message.

  • Rationale: As the format parameter is required to specify file format for the /continuous/bytes endpoint, this test asserts malformed requests raise an error.

  • Request:

GET /continuous/bytes
Accept: application/octet-stream, application/vnd.loom, text/tab-separated-values

  • Successful Response:

HTTP/1.1 400 Bad Request
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

{
  "message": "Input payload validation failed"
}

  • Success Criteria: Status Code == 4xx AND response body is valid Error json

  • Failure Criteria: Status Code != 4xx AND response body is NOT valid Error json

Continuous Bytes - Start Specified Without Chr

  • Route: /continuous/bytes

  • Description: Requests joined continuous matrix as bytes, specifying a start position without a chromosome. Expects a 400 Bad Request status code in the response, and an error message

  • Rationale: Asserts that the /continuous/bytes endpoint raises an error when start is specified without chr

  • Request:

GET /continuous/bytes?format=loom&start=5
Accept: application/octet-stream, application/vnd.loom, text/tab-separated-values

  • Successful Response:

HTTP/1.1 400 Bad Request
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

{
  "message": "chr required if either start or end is specified"
}

  • Success Criteria: Status Code == 400 AND response body is valid Error json

  • Failure Criteria: Status Code != 400 OR response body is NOT valid Error json

Continuous Bytes - End Specified Without Chr

  • Route: /continuous/bytes

  • Description: Requests joined continuous matrix as bytes, specifying an end position without a chromosome. Expects a 400 Bad Request status code in the response, and an error message

  • Rationale: Asserts that the /continuous/bytes endpoint raises an error when end is specified without chr

  • Request:

GET /continuous/bytes?format=loom&end=1000
Accept: application/octet-stream, application/vnd.loom, text/tab-separated-values

  • Successful Response:

HTTP/1.1 400 Bad Request
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

{
  "message": "chr required if either start or end is specified"
}

  • Success Criteria: Status Code == 400 AND response body is valid Error json

  • Failure Criteria: Status Code != 400 OR response body is NOT valid Error json

Continuous Bytes - Start Greater Than End

  • Route: /continuous/bytes

  • Description: Requests joined continuous matrix as bytes, specifying chr, start, and end, however, start position is greater than end. Expects a 400 Bad Request status code in the response, and an error message

  • Rationale: Asserts that the /continuous/bytes endpoint raises an error when start is greater than end

  • Request:

GET /continuous/bytes?format=loom&chr=1&start=200&end=100
Accept: application/octet-stream, application/vnd.loom, text/tab-separated-values

  • Successful Response:

HTTP/1.1 400 Bad Request
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

{
  "message": "start cannot be greater than end"
}

  • Success Criteria: Status Code == 400 AND response body is valid Error json

  • Failure Criteria: Status Code != 400 OR response body is NOT valid Error json

Continuous API Non-Implemented Test Cases

Continuous Formats Not Implemented

  • Route: /continuous/formats

  • Description: If Continuous endpoints are Not Implemented, then request /continuous/formats, expecting a 501 Not Implemented status code response

  • Rationale: Asserts that Continuous related endpoints are correctly non-implemented

  • Request:

GET /continuous/formats
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Successful Response:

HTTP/1.1 501 Not Implemented
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

  • Success Criteria: Status Code == 501

  • Failure Criteria: Status Code != 501

Continuous Ticket By Id Not Implemented

  • Route: /continuous/<id>/ticket

  • Description: If Continuous endpoints are Not Implemented, then request /continuous/<id>/ticket, expecting a 501 Not Implemented status code response

  • Rationale: Asserts that Continuous related endpoints are correctly non-implemented

  • Request:

GET /continuous/nonexistentid9999999999999999999/ticket
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Successful Response:

HTTP/1.1 501 Not Implemented
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

  • Success Criteria: Status Code == 501

  • Failure Criteria: Status Code != 501

Continuous Bytes By Id Not Implemented

  • Route: /continuous/<id>/bytes

  • Description: If Continuous endpoints are Not Implemented, then request /continuous/<id>/bytes, expecting a 501 Not Implemented status code response

  • Rationale: Asserts that Continuous related endpoints are correctly non-implemented

  • Request:

GET /continuous/nonexistentid9999999999999999999/bytes
Accept: application/octet-stream, application/vnd.loom, text/tab-separated-values

  • Successful Response:

HTTP/1.1 501 Not Implemented
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

  • Success Criteria: Status Code == 501

  • Failure Criteria: Status Code != 501

Continuous Filters Not Implemented

  • Route: /continuous/filters

  • Description: If Continuous endpoints are Not Implemented, then request /continuous/filters, expecting a 501 Not Implemented status code response

  • Rationale: Asserts that Continuous related endpoints are correctly non-implemented

  • Request:

GET /continuous/filters
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Successful Response:

HTTP/1.1 501 Not Implemented
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

  • Success Criteria: Status Code == 501

  • Failure Criteria: Status Code != 501

Continuous Ticket Not Implemented

  • Route: /continuous/ticket

  • Description: If Continuous endpoints are Not Implemented, then request /continuous/ticket, expecting a 501 Not Implemented status code response

  • Rationale: Asserts that Continuous related endpoints are correctly non-implemented

  • Request:

GET /continuous/ticket?format=loom
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Successful Response:

HTTP/1.1 501 Not Implemented
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

  • Success Criteria: Status Code == 501

  • Failure Criteria: Status Code != 501

Continuous Bytes Not Implemented

  • Route: /continuous/bytes

  • Description: If Continuous endpoints are Not Implemented, then request /continuous/bytes, expecting a 501 Not Implemented status code response

  • Rationale: Asserts that Continuous related endpoints are correctly non-implemented

  • Request:

GET /continuous/bytes?format=loom
Accept: application/octet-stream, application/vnd.loom, text/tab-separated-values

  • Successful Response:

HTTP/1.1 501 Not Implemented
Content-Type: application/vnd.ga4gh.rnaget.v1.0.0+json

  • Success Criteria: Status Code == 501

  • Failure Criteria: Status Code != 501

Continuous Content Tests

Continuous content tests assert that continuous matrices downloaded from the RNAget server contain the expected content based on the request. Continuous file tracks, positions, and intensity values are cross-referenced against the request to ensure the expected data has been returned.

Continuous Content Test Cases

Continuous Ticket by Id Content Test Cases

  • Route: /continuous/<id>/ticket

  • Description: Download test continuous matrix by ticket multiple times (sometimes slicing by chr, start, end).

  • Rationale: Asserts correct matrix file is associated with the test continuous id. Validates signal intensity values match expected. Validates returned columns/rows match expected based on slice parameters.

  • Request:

GET /continuous/5e22e009f41fc53cbea094a41de8798f/ticket
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Success Criteria: Test continuous matrix columns, rows, values match expected

  • Failure Criteria: Test continuous matrix columns, rows, values DO NOT match expected

Continuous Bytes by Id Content Test Cases

  • Route: /continuous/<id>/bytes

  • Description: Download test continuous matrix bytes multiple times (sometimes slicing by chr, start, end).

  • Rationale: Asserts correct matrix file is associated with the test continuous id. Validates signal intensity values match expected. Validates returned columns/rows match expected based on slice parameters.

  • Request:

GET /continuous/5e22e009f41fc53cbea094a41de8798f/bytes
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Success Criteria: Test continuous matrix columns, rows, values match expected

  • Failure Criteria: Test continuous matrix columns, rows, values DO NOT match expected

Continuous Ticket Content Test Cases

  • Route: /continuous/ticket

  • Description: Download joined continuous matrix by ticket multiple times (sometimes slicing by chr, start, end).

  • Rationale: Asserts joined matrix. Validates signal intensity values match expected. Validates returned columns/rows match expected based on slice parameters.

  • Request:

GET /continuous/ticket?format=loom
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Success Criteria: Joined continuous matrix columns, rows, values match expected

  • Failure Criteria: Joined continuous matrix columns, rows, values DO NOT match expected

Continuous Bytes Content Test Cases

  • Route: /continuous/bytes

  • Description: Download joined continuous matrix as bytes multiple times (sometimes slicing by chr, start, end).

  • Rationale: Asserts joined matrix. Validates signal intensity values match expected. Validates returned columns/rows match expected based on slice parameters.

  • Request:

GET /continuous/bytes?format=loom
Accept: application/vnd.ga4gh.rnaget.v1.0.0+json, application/json

  • Success Criteria: Joined continuous matrix columns, rows, values match expected

  • Failure Criteria: Joined continuous matrix columns, rows, values DO NOT match expected