Total tests: 13
Total tests passed: 11
Total tests failed: 2
Total tests skipped: 0
Total warnings generated: 2
Tests
Test: Project Get - PASSED
description: Requests the /projects/:id endpoint
summary: 'Get Project by Id' endpoint correctly implemented
API Route Test Cases - PASSED
API Test Case: Get Test Project - PASSED
case description: request /projects/:id using test project id. checks content type and status code (200). validates response body matches Project object schema.
case summary: Test project successfully retrieved
API Test Case: Project Not Found - PASSED
case description: request /projects/:id using a project id known to not exist. Checks content type and status code (4xx). Validates response body matches Error schema.
case summary: Server sends correct response when requested project not found
Test: Project Filters - PASSED
description: requests the /projects/filters endpoint
summary: 'Project Filters' endpoint correctly implemented
API Route Test Cases - PASSED
API Test Case: Project Filters - PASSED
case description: request /projects/filters. checks content type and status code (200). validates response body matches search filter array schema.
case summary: Project filters successfully retrieved
Test: Project Search - PASSED
description: Requests the /projects endpoint
summary: 'Project Search' endpoint correctly implemented
API Route Test Cases - PASSED
API Test Case: Search Projects Without Filters - PASSED
case description: request /projects without any parameter filters. checks content type and status code (200). validates response body matches project array schema.
case summary: Projects can be searched without filters
API Test Case: Search Projects With All Filters - PASSED
case description: request /projects using all server-supported project filters. checks content type and status code (200). validates response body matches project array schema.
case summary: Projects can be searched with all filters specified
API Test Case: Search Projects With Single Filter, 1 - PASSED
case description: request /projects using the first parameter filter supported by server. checks type and status code (200). validates response body matches project array schema
case summary: Projects can be searched when first filter parameter is supplied
API Test Case: Search Projects With Single Filter, 2 - PASSED
case description: request /projects using the second parameter filter supported by server. checks type and status code (200). validates response body matches project array schema
case summary: Projects can be searched when second filter parameter is supplied
API Test Case: Project Search Filters Non-Matching Resources - PASSED
case description: request /projects using filters that do not apply to any project. checks content type and status code (200). validates response body is an empty array.
case summary: Project search endpoint filters non-matching resources
Tests
Test: Study Get - PASSED
description: Requests the /studies/id endpoint
summary: 'Get Study by Id' endpoint correctly implemented
API Route Test Cases - PASSED
API Test Case: Get Test Study - PASSED
case description: request /studies/:id using test study id. checks content type and status code (200). validates response body matches Study object schema.
case summary: Test study successfully retrieved
API Test Case: Study Not Found - PASSED
case description: request /studies/:id using a study id known to not exist. Checks content type and status code (4xx). Validates response body matches Error schema.
case summary: Server sends correct response when requested study not found
Test: Study Filters - PASSED
description: requests the /studies/filters endpoint
summary: 'Study Filters' endpoint correctly implemented
API Route Test Cases - PASSED
API Test Case: Study Filters - PASSED
case description: request /studies/filters. checks content type and status code (200). validates response body matches search filter array schema.
case summary: Study filters successfully retrieved
Test: Study Search - PASSED
description: Requests the /studies endpoint
summary: 'Study Search' endpoint correctly implemented
API Route Test Cases - PASSED
API Test Case: Search Studies Without Filters - PASSED
case description: request /studies without any parameter filters. checks content type and status code (200). validates response body matches study array schema.
case summary: Studies can be searched without filters
API Test Case: Search Studies With All Filters - PASSED
case description: request /studies using all server-supported study filters. checks content type and status code (200). validates response body matches study array schema.
case summary: Studies can be searched with all filters specified
API Test Case: Search Studies With Single Filter, 1 - PASSED
case description: request /studies using the first parameter filter supported by server. checks type and status code (200). validates response body matches study array schema
case summary: Studies can be searched when first filter parameter is supplied
API Test Case: Search Studies With Single Filter, 2 - PASSED
case description: request /studies using the second parameter filter supported by server. checks type and status code (200). validates response body matches study array schema
case summary: Studies can be searched when second filter parameter is supplied
API Test Case: Study Search Filters Non-Matching Resources - PASSED
case description: request /studies using filters that do not apply to any project. checks content type and status code (200). validates response body is an empty array.
case summary: Study search endpoint filters non-matching resources
Tests
Test: Expression Formats - PASSED
description: Requests the /expressions/formats endpoint
summary: 'Expression Formats' endpoint correctly implemented
API Route Test Cases - PASSED
API Test Case: Get Supported Expression Formats - PASSED
case description: request /expressions/formats. checks content type and status code (200). validates response body is an array of strings.
case summary: Expression formats successfully retrieved
Test: Single Expression Ticket - FAILED
description: Requests the /expressions/:id/ticket endpoint
summary: 'Single Expression Ticket by Id' endpoint NOT correctly implemented
API Route Test Cases - PASSED
API Test Case: Get Test Expression Ticket - PASSED
case description: request /expressions/:id/ticket using test expression id. checks content type and status code (200). validates response body matches Ticket schema.
case summary: Test expression ticket successfully retrieved
API Test Case: Single Expression Ticket - Not Found - PASSED
case description: request /expressions/:id/ticket using an expression id known to not exist. Checks content type and status code (4xx). validates response body matches Error schema.
case summary: Server sends correct response when requested expression not found
File Content Test Cases - FAILED
Content Test Case: Single Expression Ticket - Expression Value 1 - FAILED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content DOES NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'single_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Content Test Case: Single Expression Ticket - Expression Value 2 - FAILED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content DOES NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'single_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Content Test Case: Single Expression Ticket - Expression Value 3 - FAILED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content DOES NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'single_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Content Test Case: Single Expression Ticket - Expression Value 4 - FAILED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content DOES NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'single_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Content Test Case: Single Expression Ticket - Expression Value 5 - FAILED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content DOES NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'single_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Content Test Case: Single Expression Ticket - Expression Value 6 - FAILED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content DOES NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'single_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Content Test Case: Single Expression Ticket - Expression Value 7 - FAILED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content DOES NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'single_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Content Test Case: Single Expression Ticket - Expression Value 8 - FAILED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content DOES NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'single_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Content Test Case: Single Expression Ticket - Expression Value 9 - FAILED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content DOES NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'single_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Content Test Case: Single Expression Ticket - Expression Value 10 - FAILED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content DOES NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'single_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Content Test Case: Single Expression Ticket - Slice by featureIDList - FAILED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content DOES NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'single_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Content Test Case: Single Expression Ticket - Slice by featureNameList - FAILED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content DOES NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'single_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Content Test Case: Single Expression Ticket - Slice by sampleIDList - FAILED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content DOES NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'single_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Content Test Case: Single Expression Ticket - slice by featureIDList and sampleIDList - FAILED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content DOES NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'single_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Content Test Case: Single Expression Ticket - slice by featureNameList and sampleIDList - FAILED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content DOES NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'single_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Test: Single Expression Bytes - PASSED
description: Requests the /expressions/:id/bytes endpoint
summary: 'Single Expression Bytes by Id' endpoint correctly implemented
API Route Test Cases - PASSED
API Test Case: Get Test Expression Bytes - PASSED
case description: request /expressions/:id/bytes using test expression id. checks content type and status code (200).
case summary: Test expression bytes successfully retrieved
API Test Case: Single Expression Bytes - Not Found - PASSED
case description: request /expressions/:id/bytes using an expression id known to not exist. Checks content type and status code (4xx). validates response body matches Error schema.
case summary: Server sends correct response when requested expression not found
File Content Test Cases - PASSED
Content Test Case: Single Expression Bytes - Expression Value 1 - PASSED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content matches expected
Content Test Case: Single Expression Bytes - Expression Value 2 - PASSED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content matches expected
Content Test Case: Single Expression Bytes - Expression Value 3 - PASSED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content matches expected
Content Test Case: Single Expression Bytes - Expression Value 4 - PASSED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content matches expected
Content Test Case: Single Expression Bytes - Expression Value 5 - PASSED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content matches expected
Content Test Case: Single Expression Bytes - Expression Value 6 - PASSED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content matches expected
Content Test Case: Single Expression Bytes - Expression Value 7 - PASSED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content matches expected
Content Test Case: Single Expression Bytes - Expression Value 8 - PASSED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content matches expected
Content Test Case: Single Expression Bytes - Expression Value 9 - PASSED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content matches expected
Content Test Case: Single Expression Bytes - Expression Value 10 - PASSED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content matches expected
Content Test Case: Single Expression Bytes - Slice by featureIDList - PASSED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content matches expected
Content Test Case: Single Expression Bytes - Slice by featureNameList - PASSED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content matches expected
Content Test Case: Single Expression Bytes - Slice by sampleIDList - PASSED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content matches expected
Content Test Case: Single Expression Bytes - slice by featureIDList and sampleIDList - PASSED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content matches expected
Content Test Case: Single Expression Bytes - slice by featureNameList and sampleIDList - PASSED
case description: Asserts correct expression values and slicing operations
case summary: Expression matrix content matches expected
Test: Expression Filters - PASSED
description: Requests the /expressions/filters endpoint.
summary: 'Expression Filters' endpoint correctly implemented
API Route Test Cases - PASSED
API Test Case: Expression Filters - PASSED
case description: request /expressions/filters. checks content type and status code (200). validates response body matches search filter array schema.
case summary: Expression filters successfully retrieved
Test: Multi Expression Ticket - FAILED
description: Requests the /expressions/ticket endpoint.
summary: 'Expression Ticket' endpoint NOT correctly implemented
API Route Test Cases - PASSED
API Test Case: Expression Ticket by Format - PASSED
case description: requests /expressions/ticket, only specifying the required 'format' parameter. checks content type and status code (200). validates response body matches ticket schema
case summary: Expression Ticket can be retrieved
API Test Case: Expression Ticket - All Filters - PASSED
case description: request /expressions/ticket using all server-supported expression filters. checks content type and status code (200). validates response body matches ticket schema.
case summary: Expression Ticket retrieved when all filters specified
API Test Case: Expression Ticket - Single Filter, 1 - PASSED
case description: request /expressions/ticket using the first filter supported by server (in addition to format). checks type and status code (200). validates response body matches ticket schema
case summary: Expression Ticket retrieved when first filter supplied
API Test Case: Expression Ticket - Single Filter, 2 - PASSED
case description: request /expressions/ticket using the second filter supported by server (in addition to format). checks type and status code (200). validates response body matches ticket schema
case summary: Expression Ticket retrieved when second filter supplied
API Test Case: Expression Ticket - Format Not Specified - PASSED
case description: request /expressions/ticket endpoint without specifying the required 'format' parameter. checks content type and status code (4xx). validates response body matches error schema.
case summary: Server returns error when format not specified
API Test Case: Expression Ticket - Filetype Matches - PASSED
case description: request /expressions/ticket endpoint with 'format' parameter specified. checks content type and status code (200). validates ticket fileType matches requested format.
case summary: Expression Ticket fileType matches request format
File Content Test Cases - FAILED
Content Test Case: Multi Expression Ticket - Expression Value 1 - FAILED
case description: Asserts correct slicing/subsetting of expression matrix when slice parameters are passed to /expressions/ticket
case summary: Sliced expression matrix rows, columns, and values DO NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'multi_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Content Test Case: Multi Expression Ticket - Expression Value 2 - FAILED
case description: Asserts correct slicing/subsetting of expression matrix when slice parameters are passed to /expressions/ticket
case summary: Sliced expression matrix rows, columns, and values DO NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'multi_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Content Test Case: Multi Expression Ticket - Expression Value 3 - FAILED
case description: Asserts correct slicing/subsetting of expression matrix when slice parameters are passed to /expressions/ticket
case summary: Sliced expression matrix rows, columns, and values DO NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'multi_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Content Test Case: Multi Expression Ticket - Expression Value 4 - FAILED
case description: Asserts correct slicing/subsetting of expression matrix when slice parameters are passed to /expressions/ticket
case summary: Sliced expression matrix rows, columns, and values DO NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'multi_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Content Test Case: Multi Expression Ticket - Expression Value 5 - FAILED
case description: Asserts correct slicing/subsetting of expression matrix when slice parameters are passed to /expressions/ticket
case summary: Sliced expression matrix rows, columns, and values DO NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'multi_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Content Test Case: Multi Expression Ticket - Slice by featureIDList - FAILED
case description: Asserts correct slicing/subsetting of expression matrix when slice parameters are passed to /expressions/ticket
case summary: Sliced expression matrix rows, columns, and values DO NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'multi_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Content Test Case: Multi Expression Ticket - Slice by featureNameList - FAILED
case description: Asserts correct slicing/subsetting of expression matrix when slice parameters are passed to /expressions/ticket
case summary: Sliced expression matrix rows, columns, and values DO NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'multi_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Content Test Case: Multi Expression Ticket - Slice by sampleIDList - FAILED
case description: Asserts correct slicing/subsetting of expression matrix when slice parameters are passed to /expressions/ticket
case summary: Sliced expression matrix rows, columns, and values DO NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'multi_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Content Test Case: Multi Expression Ticket - slice by featureIDList and sampleIDList - FAILED
case description: Asserts correct slicing/subsetting of expression matrix when slice parameters are passed to /expressions/ticket
case summary: Sliced expression matrix rows, columns, and values DO NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'multi_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Content Test Case: Multi Expression Ticket - slice by featureNameList and sampleIDList - FAILED
case description: Asserts correct slicing/subsetting of expression matrix when slice parameters are passed to /expressions/ticket
case summary: Sliced expression matrix rows, columns, and values DO NOT match expected
error message: Error parsing expression json and download url: Unable to create file (unable to open file: name = 'multi_expression_ticket_content_test.loom', errno = 17, error message = 'File exists', flags = 15, o_flags = c2)
Test: Multi Expression Bytes - PASSED
description: Requests the /expressions/bytes endpoint.
summary: 'Expression Bytes' endpoint correctly implemented
API Route Test Cases - PASSED
API Test Case: Expression Bytes by Format - PASSED
case description: requests /expressions/bytes, only specifying the required 'format' parameter. checks content type and status code (200).
case summary: Expression Bytes can be retrieved
API Test Case: Expression Bytes - All Filters - PASSED
case description: request /expressions/bytes using all server-supported expression filters. checks content type and status code (200).
case summary: Expression Bytes retrieved when all filters specified
API Test Case: Expression Bytes - Single Filter, 1 - PASSED
case description: request /expressions/bytes using the first filter supported by server (in addition to format). checks type and status code (200).
case summary: Expression Bytes retrieved when first filter supplied
API Test Case: Expression Bytes - Single Filter, 2 - PASSED
case description: request /expressions/bytes using the second filter supported by server (in addition to format). checks type and status code (200).
case summary: Expression Bytes retrieved when second filter supplied
API Test Case: Expression Bytes - Format Not Specified - PASSED
case description: request /expressions/bytes endpoint without specifying the required 'format' parameter. checks content type and status code (4xx). validates response body matches error schema.
case summary: Server returns error when format not specified
File Content Test Cases - PASSED
Content Test Case: Multi Expression Bytes - Expression Value 6 - PASSED
case description: Asserts correct slicing/subsetting of expression matrix when slice parameters are passed to endpoint
case summary: Sliced expression matrix rows, columns, and values match expected
Content Test Case: Multi Expression Bytes - Expression Value 7 - PASSED
case description: Asserts correct slicing/subsetting of expression matrix when slice parameters are passed to endpoint
case summary: Sliced expression matrix rows, columns, and values match expected
Content Test Case: Multi Expression Bytes - Expression Value 8 - PASSED
case description: Asserts correct slicing/subsetting of expression matrix when slice parameters are passed to endpoint
case summary: Sliced expression matrix rows, columns, and values match expected
Content Test Case: Multi Expression Bytes - Expression Value 9 - PASSED
case description: Asserts correct slicing/subsetting of expression matrix when slice parameters are passed to endpoint
case summary: Sliced expression matrix rows, columns, and values match expected
Content Test Case: Multi Expression Bytes - Expression Value 10 - PASSED
case description: Asserts correct slicing/subsetting of expression matrix when slice parameters are passed to endpoint
case summary: Sliced expression matrix rows, columns, and values match expected
Content Test Case: Multi Expression Bytes - Slice by featureIDList - PASSED
case description: Asserts correct slicing/subsetting of expression matrix when slice parameters are passed to endpoint
case summary: Sliced expression matrix rows, columns, and values match expected
Content Test Case: Multi Expression Bytes - Slice by featureNameList - PASSED
case description: Asserts correct slicing/subsetting of expression matrix when slice parameters are passed to endpoint
case summary: Sliced expression matrix rows, columns, and values match expected
Content Test Case: Multi Expression Bytes - Slice by sampleIDList - PASSED
case description: Asserts correct slicing/subsetting of expression matrix when slice parameters are passed to endpoint
case summary: Sliced expression matrix rows, columns, and values match expected
Content Test Case: Multi Expression Bytes - slice by featureIDList and sampleIDList - PASSED
case description: Asserts correct slicing/subsetting of expression matrix when slice parameters are passed to endpoint
case summary: Sliced expression matrix rows, columns, and values match expected
Content Test Case: Multi Expression Bytes - slice by featureNameList and sampleIDList - PASSED
case description: Asserts correct slicing/subsetting of expression matrix when slice parameters are passed to endpoint
case summary: Sliced expression matrix rows, columns, and values match expected
Tests
Test: Continuous Endpoint Not Implemented - PASSED
description: Requests various /continuous routes, expecting the service to respond with a 'Not Implemented' status code
summary: Continuous endpoints correctly non-implemented
API Route Test Cases - PASSED
API Test Case: Continuous Formats Not Implemented - PASSED
case description: request /continuous/formats, expecting 501 status code
case summary: Continuous Formats correctly non-implemented
API Test Case: Continuous Ticket by Id Not Implemented - PASSED
case description: request /continuous/:id/ticket, expecting 501 status code
case summary: Continuous Ticket by Id correctly non-implemented
API Test Case: Continuous Bytes by Id Not Implemented - PASSED
case description: request /continuous/:id/bytes, expecting 501 status code
case summary: Continuous Bytes by Id correctly non-implemented
API Test Case: Continuous Filters Not Implemented - PASSED
case description: request /continuous/filters, expecting 501 status code
case summary: Continuous Filters correctly non-implemented
API Test Case: Continuous Ticket Not Implemented - PASSED
case description: request /continuous/ticket, expecting 501 status code
case summary: Continuous Ticket correctly non-implemented
API Test Case: Continuous Bytes Not Implemented - PASSED
case description: request /continuous/bytes, expecting 501 status code
case summary: Continuous Bytes correctly non-implemented
Server name | Object and Id | Test case | Status |
---|---|---|---|
CanDIG | Projects: 9c0eba51095d3939437e220db196e27b | Project Get | PASSED |
CanDIG | Projects: 9c0eba51095d3939437e220db196e27b | Project Filters | PASSED |
CanDIG | Projects: 9c0eba51095d3939437e220db196e27b | Project Search | PASSED |
CanDIG | Studies: f3ba0b59bed0fa2f1030e7cb508324d1 | Study Get | PASSED |
CanDIG | Studies: f3ba0b59bed0fa2f1030e7cb508324d1 | Study Filters | PASSED |
CanDIG | Studies: f3ba0b59bed0fa2f1030e7cb508324d1 | Study Search | PASSED |
CanDIG | Expressions: ac3e9279efd02f1c98de4ed3d335b98e | Expression Formats | PASSED |
CanDIG | Expressions: ac3e9279efd02f1c98de4ed3d335b98e | Single Expression Ticket | FAILED |
CanDIG | Expressions: ac3e9279efd02f1c98de4ed3d335b98e | Single Expression Bytes | PASSED |
CanDIG | Expressions: ac3e9279efd02f1c98de4ed3d335b98e | Expression Filters | PASSED |
CanDIG | Expressions: ac3e9279efd02f1c98de4ed3d335b98e | Multi Expression Ticket | FAILED |
CanDIG | Expressions: ac3e9279efd02f1c98de4ed3d335b98e | Multi Expression Bytes | PASSED |
CanDIG | Continuous: NA | Continuous Endpoint Not Implemented | PASSED |