Skip to content

Instantly share code, notes, and snippets.

@ChrisRus

ChrisRus/ARCcore-v0.0.18-rc0-test-output.txt

Created February 21, 2018 16:30
Show Gist options
  • Save ChrisRus/d1bf644cbd69ab2796bc8ff83b94b632 to your computer and use it in GitHub Desktop.
Save ChrisRus/d1bf644cbd69ab2796bc8ff83b94b632 to your computer and use it in GitHub Desktop.
Download ZIP
ARCcore v0.0.18 RC0 Build & Test Run Output
Raw
ARCcore-v0.0.18-rc0-test-output.txt
[08:24:01] Using gulpfile ~/code/encapsule/ARC_master/gulpfile.js
[08:24:01] Starting 'copyjs_graph'...
copyjs_graph
[08:24:01] Starting 'copyjs_tools'...
copyjs_tools
[08:24:01] Starting 'copyjs_tools_templates'...
copyjs_tools
[08:24:01] Starting 'coffee.base'...
[08:24:01] Starting 'coffee.discriminator'...
[08:24:01] Starting 'coffee.filter'...
[08:24:01] Starting 'coffee.filter-dag'...
[08:24:01] Starting 'coffee.identifier'...
[08:24:01] Starting 'coffee.types'...
[08:24:01] Starting 'coffee.util'...
[08:24:02] Finished 'copyjs_tools_templates' after 541 ms
[08:24:02] Finished 'coffee.base' after 540 ms
[08:24:02] Finished 'coffee.util' after 528 ms
[08:24:03] Finished 'coffee.identifier' after 1.3 s
[08:24:03] Finished 'coffee.types' after 1.38 s
[08:24:03] Finished 'coffee.discriminator' after 1.46 s
[08:24:03] Finished 'coffee.filter' after 1.46 s
[08:24:03] Finished 'copyjs_graph' after 1.63 s
[08:24:03] Finished 'copyjs_tools' after 1.63 s
[08:24:03] Starting 'copyjs'...
copyjs...
[08:24:03] Finished 'copyjs' after 40 μs
[08:24:03] Finished 'coffee.filter-dag' after 1.62 s
[08:24:03] Starting 'coffee'...
coffee...
[08:24:03] Finished 'coffee' after 22 μs
[08:24:03] Starting 'baseBuild'...
baseBuild...
[08:24:03] Finished 'baseBuild' after 20 μs
[08:24:03] Starting 'test'...
> loading module under test '../../BUILD/arccore/arc_core_digraph_in_params'...
> loading module under test '../../BUILD/arccore/arc_core_digraph'...
> loading module under test '../../BUILD/arccore/arc_core_digraph'...
> loading module under test '../../BUILD/arccore/arc_core_digraph'...
> loading module under test '../../BUILD/arccore/arc_core_digraph_algorithm_transpose'...
> loading module under test '../../BUILD/arccore/arc_core_digraph'...
> loading module under test '../../BUILD/arccore/arc_core_digraph_algorithm_context'...
> loading module under test '../../BUILD/arccore/arc_core_digraph'...
> loading module under test '../../BUILD/arccore/arc_core_digraph_algorithm_context'...
> loading module under test '../../BUILD/arccore/arc_core_digraph_algorithm_request'...
> loading module under test '../../BUILD/arccore/arc_core_digraph'...
> loading module under test '../../BUILD/arccore/arc_core_digraph_algorithm_context'...
> loading module under test '../../BUILD/arccore/arc_core_digraph_algorithm_visit'...
> loading module under test '../../BUILD/arccore/arc_core_digraph'...
> loading module under test '../../BUILD/arccore/arc_core_digraph_algorithm_bft'...
> loading module under test '../../BUILD/arccore/arc_core_digraph'...
> loading module under test '../../BUILD/arccore/arc_core_digraph_algorithm_dft'...
> loading module under test '../../BUILD/arccore/arc_core_graph'...
> loading module under test '../../BUILD/arccore/arc_core_digraph'...
> loading module under test '../../BUILD/arccore/arc_core_types_convert'...
> loading module under test '../../BUILD/arccore/arc_core_types_check'...
> loading module under test '../../BUILD/arccore/arc_core_identifier_irut'...
> loading module under test '../../BUILD/arccore/arc_core_identifier_irut'...
> loading module under test '../../BUILD/arccore/arc_core_filter_create'...
> loading module under test '../../BUILD/arccore/arc_core_filter_runtime'...
> loading module under test '../../BUILD/arccore/arc_core_filter_runtime_spec_processor'...
> loading module under test '../../BUILD/arccore/arc_core_filter_create'...
> loading module under test '../../BUILD/arccore/arc_core_filter_create'...
> loading module under test '../../BUILD/arccore/arc_core_filter_create'...
> loading module under test '../../BUILD/arccore/arc_core_filter_create'...
> loading module under test '../../BUILD/arccore/arc_core_filter_create'...
> loading module under test '../../BUILD/arccore/arc_core_filter_create'...
> loading module under test '../../BUILD/arccore/arc_core_filter_create'...
> loading module under test '../../BUILD/arccore/arc_core_filter_create'...
> loading module under test '../../BUILD/arccore/arc_core_type_discriminator_merged_model_digraph'...
> loading module under test '../../BUILD/arccore/arc_core_filter'...
> loading module under test '../../BUILD/arccore/arc_core_type_discriminator_merged_model_digraph'...
> loading module under test '../../BUILD/arccore/arc_core_type_discriminator_ambiguity_detector'...
> loading module under test '../../BUILD/arccore/arc_core_type_discriminator_merged_model_digraph'...
> loading module under test '../../BUILD/arccore/arc_core_type_discriminator_ambiguity_detector'...
> loading module under test '../../BUILD/arccore/arc_core_type_discriminator_runtime_parse_digraph'...
> loading module under test '../../BUILD/arccore/arc_core_type_discriminator_factory'...
> loading module under test '../../BUILD/arccore/arc_core_type_discriminator_factory'...
> loading module under test '../../BUILD/arccore/arc_core'...
ARC_master TEST SUITE:
**** ARC_core Test Suite ****
DirectedGraph in-parameter validator `verifyVertexReadRequest' test: Undefined request:
✓ The 'verifyVertexReadRequest' function should have returned a response object.
The test asserts the request to be invalid. Verify the response contains the expected error.
✓ The request normalizer should not have returned a result.
✓ The request normalizer should have returned an error string.
✓ The error string should match the expected control value.
DirectedGraph in-parameter validator `verifyVertexReadRequest' test: Bad request type:
✓ The 'verifyVertexReadRequest' function should have returned a response object.
The test asserts the request to be invalid. Verify the response contains the expected error.
✓ The request normalizer should not have returned a result.
✓ The request normalizer should have returned an error string.
✓ The error string should match the expected control value.
DirectedGraph in-parameter validator `verifyVertexReadRequest' test: Valid request:
✓ The 'verifyVertexReadRequest' function should have returned a response object.
The test asserts the request to be valid. Verify the response contains the expected result.
✓ The request normalizer should not have returned an error.
✓ The request normalizer should have returned a result.
✓ The result JSON should match the expected control value.
DirectedGraph in-parameter validator `verifyVertexWriteRequest' test: Missing request:
✓ The 'verifyVertexWriteRequest' function should have returned a response object.
The test asserts the request to be invalid. Verify the response contains the expected error.
✓ The request normalizer should not have returned a result.
✓ The request normalizer should have returned an error string.
✓ The error string should match the expected control value.
DirectedGraph in-parameter validator `verifyVertexWriteRequest' test: Empty request:
✓ The 'verifyVertexWriteRequest' function should have returned a response object.
The test asserts the request to be invalid. Verify the response contains the expected error.
✓ The request normalizer should not have returned a result.
✓ The request normalizer should have returned an error string.
✓ The error string should match the expected control value.
DirectedGraph in-parameter validator `verifyVertexWriteRequest' test: Bad 'u' type:
✓ The 'verifyVertexWriteRequest' function should have returned a response object.
The test asserts the request to be invalid. Verify the response contains the expected error.
✓ The request normalizer should not have returned a result.
✓ The request normalizer should have returned an error string.
✓ The error string should match the expected control value.
DirectedGraph in-parameter validator `verifyVertexWriteRequest' test: Valid 'u':
✓ The 'verifyVertexWriteRequest' function should have returned a response object.
The test asserts the request to be valid. Verify the response contains the expected result.
✓ The request normalizer should not have returned an error.
✓ The request normalizer should have returned a result.
✓ The result JSON should match the expected control value.
DirectedGraph in-parameter validator `verifyVertexWriteRequest' test: Invalid 'p' type:
✓ The 'verifyVertexWriteRequest' function should have returned a response object.
The test asserts the request to be invalid. Verify the response contains the expected error.
✓ The request normalizer should not have returned a result.
✓ The request normalizer should have returned an error string.
✓ The error string should match the expected control value.
DirectedGraph in-parameter validator `verifyVertexWriteRequest' test: Valid full request:
✓ The 'verifyVertexWriteRequest' function should have returned a response object.
The test asserts the request to be valid. Verify the response contains the expected result.
✓ The request normalizer should not have returned an error.
✓ The request normalizer should have returned a result.
✓ The result JSON should match the expected control value.
DirectedGraph in-parameter validator `verifyEdgeReadRequest' test: Missing request:
✓ The 'verifyEdgeReadRequest' function should have returned a response object.
The test asserts the request to be invalid. Verify the response contains the expected error.
✓ The request normalizer should not have returned a result.
✓ The request normalizer should have returned an error string.
✓ The error string should match the expected control value.
DirectedGraph in-parameter validator `verifyEdgeReadRequest' test: Bad 'u':
✓ The 'verifyEdgeReadRequest' function should have returned a response object.
The test asserts the request to be invalid. Verify the response contains the expected error.
✓ The request normalizer should not have returned a result.
✓ The request normalizer should have returned an error string.
✓ The error string should match the expected control value.
DirectedGraph in-parameter validator `verifyEdgeReadRequest' test: Bad 'v':
✓ The 'verifyEdgeReadRequest' function should have returned a response object.
The test asserts the request to be invalid. Verify the response contains the expected error.
✓ The request normalizer should not have returned a result.
✓ The request normalizer should have returned an error string.
✓ The error string should match the expected control value.
DirectedGraph in-parameter validator `verifyEdgeReadRequest' test: Valid 'v':
✓ The 'verifyEdgeReadRequest' function should have returned a response object.
The test asserts the request to be valid. Verify the response contains the expected result.
✓ The request normalizer should not have returned an error.
✓ The request normalizer should have returned a result.
✓ The result JSON should match the expected control value.
DirectedGraph in-parameter validator `verifyEdgeWriteRequest' test: Missing request:
✓ The 'verifyEdgeWriteRequest' function should have returned a response object.
The test asserts the request to be invalid. Verify the response contains the expected error.
✓ The request normalizer should not have returned a result.
✓ The request normalizer should have returned an error string.
✓ The error string should match the expected control value.
DirectedGraph in-parameter validator `verifyEdgeWriteRequest' test: Bad 'e':
✓ The 'verifyEdgeWriteRequest' function should have returned a response object.
The test asserts the request to be invalid. Verify the response contains the expected error.
✓ The request normalizer should not have returned a result.
✓ The request normalizer should have returned an error string.
✓ The error string should match the expected control value.
DirectedGraph in-parameter validator `verifyEdgeWriteRequest' test: Bad 'e.u':
✓ The 'verifyEdgeWriteRequest' function should have returned a response object.
The test asserts the request to be invalid. Verify the response contains the expected error.
✓ The request normalizer should not have returned a result.
✓ The request normalizer should have returned an error string.
✓ The error string should match the expected control value.
DirectedGraph in-parameter validator `verifyEdgeWriteRequest' test: Bad 'e.v':
✓ The 'verifyEdgeWriteRequest' function should have returned a response object.
The test asserts the request to be invalid. Verify the response contains the expected error.
✓ The request normalizer should not have returned a result.
✓ The request normalizer should have returned an error string.
✓ The error string should match the expected control value.
DirectedGraph in-parameter validator `verifyEdgeWriteRequest' test: Valid 'e':
✓ The 'verifyEdgeWriteRequest' function should have returned a response object.
The test asserts the request to be valid. Verify the response contains the expected result.
✓ The request normalizer should not have returned an error.
✓ The request normalizer should have returned a result.
✓ The result JSON should match the expected control value.
DirectedGraph in-parameter validator `verifyEdgeWriteRequest' test: Bad 'p':
✓ The 'verifyEdgeWriteRequest' function should have returned a response object.
The test asserts the request to be invalid. Verify the response contains the expected error.
✓ The request normalizer should not have returned a result.
✓ The request normalizer should have returned an error string.
✓ The error string should match the expected control value.
DirectedGraph in-parameter validator `verifyEdgeWriteRequest' test: Valid full request:
✓ The 'verifyEdgeWriteRequest' function should have returned a response object.
The test asserts the request to be valid. Verify the response contains the expected result.
✓ The request normalizer should not have returned an error.
✓ The request normalizer should have returned a result.
✓ The result JSON should match the expected control value.
DirectedGraph container object tests
Object construction tests
✓ graph should be an object
✓ graph should have zero vertices
✓ graph should have zero edges
✓ graph should have zero root vertices
✓ graph should have zero leaf vertices
Import/Export tests
✓ graph export JSON should match expected control string
✓ graph should export structured JSON string
✓ graph export to object and JSON should be identical
✓ graph constructed from export object should be identical to original
✓ empty graph filled using fromObject should be identical to original
✓ empty graph filled using fromJSON should be identical to original
Re-create the directed graph container from the JSON.
✓ graph should re-create identical graph from import
Test JSON export algorith's vertex skip facility
✓ Exported JSON should match expected JSON value.
Vertex API tests
addVertex
✓ graph should have a single vertex
✓ graph should have zero edges
✓ graph should have one root vertex
✓ graph should have one leaf vertex
✓ vertex should have zero in-degree
✓ vertex should have zero out-degree
✓ vertex in-edge array should have length zero
✓ vertex out-edge array should have length zero
addVertex (idempotency)
✓ graph should have a single vertex
✓ graph should have zero edges
✓ graph should have one root vertex
✓ graph should have one leaf vertex
✓ vertex should have zero in-degree
✓ vertex should have zero out-degree
✓ vertex in-edge array should have length zero
✓ vertex out-edge array should have length zero
removeVertex
✓ graph should have zero vertices
✓ graph should have zero edges
✓ graph should have zero root vertices
✓ graph should have zero leaf vertices
removeVertex (idempotency)
✓ graph should have zero vertices
✓ graph should have zero edges
✓ graph should have zero root vertices
✓ graph should have zero leaf vertices
Edge API tests
addEdge(apple,orange)
✓ graph should have two vertices
✓ graph should have one edge
✓ graph should have one root vertex
✓ graph should have one leaf vertex
✓ vertex 'apple' should have in-degree zero
✓ vertex 'apple' should have out-degree one
✓ vertex 'orange' should have in-degree one
✓ vertex 'orange' should have out-degree zero
✓ vertex 'apple' in-edge array should have length zero
✓ vertex 'apple' out-edge array should have length one
✓ vertex 'orange' in-edge array should have length one
✓ vertex 'orange' out-edge array should have length zero
addEdge(apple,orange) (idempotency)
✓ graph should have two vertices
✓ graph should have one edge
✓ graph should have one root vertex
✓ graph should have one leaf vertex
✓ vertex 'apple' should have in-degree zero
✓ vertex 'apple' should have out-degree one
✓ vertex 'orange' should have in-degree one
✓ vertex 'orange' should have out-degree zero
✓ vertex 'apple' in-edge array should have length zero
✓ vertex 'apple' out-edge array should have length one
✓ vertex 'orange' in-edge array should have length one
✓ vertex 'orange' out-edge array should have length zero
removeEdge(apple,orange)
✓ graph should have two vertices
✓ graph should have zero edges
✓ graph should have two root vertices
✓ graph should have two leaf vertices
✓ vertex 'apple' should have in-degree zero
✓ vertex 'apple' should have out-degree zero
✓ vertex 'orange' should have out-degree zero
✓ vertex 'orange' should have in-degree zero
✓ vertex 'apple' in-edge array should have length zero
✓ vertex 'apple' out-edge array should have length zero
✓ vertex 'orange' in-edge array should have length zero
✓ vertex 'orange' out-edge array should have length zero
removeEdge(apple,orange) idempotency
✓ graph should have two vertices
✓ graph should have zero edges
✓ graph should have two root vertices
✓ graph should have two leaf vertices
✓ vertex 'apple' should have in-degree zero
✓ vertex 'apple' should have out-degree zero
✓ vertex 'orange' should have out-degree zero
✓ vertex 'orange' should have in-degree zero
✓ vertex 'apple' in-edge array should have length zero
✓ vertex 'apple' out-edge array should have length zero
✓ vertex 'orange' in-edge array should have length zero
✓ vertex 'orange' out-edge array should have length zero
addEdge(apple,orange), removeVertex(orange)
✓ graph should have one vertex
✓ graph should have zero edges
✓ graph should have one root vertex
✓ graph should have one leaf vertex
✓ vertex 'apple' should have in-degree zero
✓ vertex 'apple' should have out-degree zero
✓ vertex in-edge array should have length zero
✓ vertex out-edge array should have length zero
ring topology tests
✓ graph should have three vertices
✓ graph should have three edges
✓ graph should have zero root vertices
✓ graph should have zero leaf vertices
✓ vertex 'blue' should have in-degree one
✓ vertex 'blue' should have out-degree one
✓ vertex 'blue' in-edge array should have length one
✓ vertex 'blue' out-edge array should have length one
cube topology tests
create cube topology tests
✓ graph should have eigth vertices
✓ graph should have twelve edges
✓ graph should have zero root vertices
✓ graph should have zero leaf vertices
✓ vertex 'north1' should have in-degree one
✓ vertex 'north1' should have out-degree two
✓ vertex 'north1' in-edge array should have length one
✓ vertex 'north1' out-edge array should have length two
remove cube corner tests
✓ graph should have seven vertices
✓ graph should have nine edges
✓ graph should have zero root vertices
✓ graph should have one leaf vertices
✓ vertex 'east2' should have in-degree two
✓ vertex 'east2' should have out-degree zero
✓ vertex 'east2' in-edge array should have length two
✓ vertex 'east2' out-edge array should have length zero
Property get/set/has/clear tests
✓ 'hasVertexProperty' on non-existent vertex should return false
✓ 'hasVertexProperty' on vertex added w/out property should return false
✓ 'hasVertexProperty' on vertex added w/property should return true
✓ 'clearVertexProperty' on non-existent vertex should return false
✓ 'clearVertexProperty' on vertex that exists should return true (regardless of if it has a property)
✓ 'hasVertexProperty' should return false on vertex w/property after it is cleared
✓ 'hasEdgeProperty' should return false on non-existent edge
✓ 'hasEdgeProperty' should return false on edge added w/no property
✓ 'hasEdgeProperty' should return true on edge added w/property
✓ 'clearEdgeProperty' should return false on non-existent edge
✓ 'clearEdgeProperty' should return true on edge that doesn't have a property
✓ 'clearEdgeProperty' should return true on edge has a property
Graph stress
✓ graph should have 1000000 vertices (160ms)
jsgraph.createDirectedGraph test: Bogus construction #1
✓ the call should have returned a response object.
✓ the call response should not have returned a result.
✓ the call response error should match the expected error string.
jsgraph.createDirectedGraph test: Bogus construction #2
✓ the call should have returned a response object.
✓ the call response should not have returned a result.
✓ the call response error should match the expected error string.
jsgraph.createDirectedGraph test: Bogus construction #3
✓ the call should have returned a response object.
✓ the call response should not have returned a result.
✓ the call response error should match the expected error string.
jsgraph.createDirectedGraph test: Bogus construction #4
✓ the call should have returned a response object.
✓ the call response should not have returned a result.
✓ the call response error should match the expected error string.
jsgraph.createDirectedGraph test: Bogus construction #5
✓ the call should have returned a response object.
✓ the call response should not have returned a result.
✓ the call response error should match the expected error string.
jsgraph.createDirectedGraph test: Bogus construction #6
✓ the call should have returned a response object.
✓ the call response should not have returned a result.
✓ the call response error should match the expected error string.
jsgraph.createDirectedGraph test: Bogus construction #7
✓ the call should have returned a response object.
✓ the call response should not have returned a result.
✓ the call response error should match the expected error string.
jsgraph.createDirectedGraph test: Bogus construction #8
✓ the call should have returned a response object.
✓ the call response should not have returned a result.
✓ the call response error should match the expected error string.
jsgraph.createDirectedGraph test: Bogus construction #9
✓ the call should have returned a response object.
✓ the call response should not have returned a result.
✓ the call response error should match the expected error string.
jsgraph.createDirectedGraph test: Bogus construction #10
✓ the call should have returned a response object.
✓ the call response should not have returned a result.
✓ the call response error should match the expected error string.
jsgraph.createDirectedGraph test: Bogus construction #11
✓ the call should have returned a response object.
✓ the call response should not have returned a result.
✓ the call response error should match the expected error string.
jsgraph.createDirectedGraph test: Bogus construction #12
✓ the call should have returned a response object.
✓ the call response should not have returned a result.
✓ the call response error should match the expected error string.
jsgraph.createDirectedGraph test: Bogus construction #13
✓ the call should have returned a response object.
✓ the call response should not have returned a result.
✓ the call response error should match the expected error string.
jsgraph.createDirectedGraph test: Default construction
✓ the call should have returned a response object.
✓ the call response should not indicate an error.
✓ the call response should have returned a DirectedGraph container object.
✓ the returned graph JSON should match expected control value.
jsgraph.createDirectedGraph test: More advanced example
✓ the call should have returned a response object.
✓ the call response should not indicate an error.
✓ the call response should have returned a DirectedGraph container object.
✓ the returned graph JSON should match expected control value.
Directed graph tranposition test
macro-level tests
✓ input digraph should contain six vertices
✓ input digraph should contain five edges
✓ input digraph should have two root vertices
✓ input digraph should have three leaf vertices
✓ output digraph should contain six vertices
✓ output digraph should contain five edges
✓ output digraph should have three root vertices
✓ output digraph should have two leaf vertices
check out-degree of roots and leaves before/after transposition
✓ inputA should have out-degree one in the input graph
✓ inputA should have out-degree zero in the output graph
✓ outputC should have out-degree zero in the input graph
✓ outputC should have out-degree one in the output graph
vertex 'process' vertex before/after transposition
✓ process should have in-degree two in the input graph
✓ process should have in-degree three in the output graph
✓ process should have out-degree three in the input graph
✓ process should have out-degree two in the output graph
Traverse context: missing request object.
✓ createTraverseContext call should have returned a response object
✓ response JSON should match expected result
Traverse context: missing digraph object.
✓ createTraverseContext call should have returned a response object
✓ response JSON should match expected result
Traverse context: constructed for a specific digraph
✓ the call to createTraverseContext should have returned a response.
✓ response JSON should match expected result
xFT request normalizer unit test: Bad input: missing request:
✓ The xFT request normalizer should have returned a response object.
The test asserts the request to be invalid. Verify the response contains the expected error.
✓ The request normalizer should not have returned a result.
✓ The request normalizer should have returned an error string.
✓ The error string should match the expected control value.
xFT request normalizer unit test: Bad input: empty request:
✓ The xFT request normalizer should have returned a response object.
The test asserts the request to be invalid. Verify the response contains the expected error.
✓ The request normalizer should not have returned a result.
✓ The request normalizer should have returned an error string.
✓ The error string should match the expected control value.
xFT request normalizer unit test: Bad input: missing 'visitor':
✓ The xFT request normalizer should have returned a response object.
The test asserts the request to be invalid. Verify the response contains the expected error.
✓ The request normalizer should not have returned a result.
✓ The request normalizer should have returned an error string.
✓ The error string should match the expected control value.
xFT request normalizer unit test: Bad input: Bad options object type:
✓ The xFT request normalizer should have returned a response object.
The test asserts the request to be invalid. Verify the response contains the expected error.
✓ The request normalizer should not have returned a result.
✓ The request normalizer should have returned an error string.
✓ The error string should match the expected control value.
xFT request normalizer unit test: Minimum viable input:
✓ The xFT request normalizer should have returned a response object.
The test asserts the request to be valid. Verify the response contains the expected result.
✓ The request normalizer should not have returned an error.
✓ The request normalizer should have returned a result.
✓ The result JSON should match the expected control value.
xFT request normalizer unit test: options.signalStart set explicitly true:
✓ The xFT request normalizer should have returned a response object.
The test asserts the request to be valid. Verify the response contains the expected result.
✓ The request normalizer should not have returned an error.
✓ The request normalizer should have returned a result.
✓ The result JSON should match the expected control value.
xFT request normalizer unit test: options.signalStart set explicitly false:
✓ The xFT request normalizer should have returned a response object.
The test asserts the request to be valid. Verify the response contains the expected result.
✓ The request normalizer should not have returned an error.
✓ The request normalizer should have returned a result.
✓ The result JSON should match the expected control value.
xFT request normalizer unit test: Bad input: options.startVector overridden with wrong type:
✓ The xFT request normalizer should have returned a response object.
The test asserts the request to be invalid. Verify the response contains the expected error.
✓ The request normalizer should not have returned a result.
✓ The request normalizer should have returned an error string.
✓ The error string should match the expected control value.
xFT request normalizer unit test: options.startVector overridden with string vertex ID:
✓ The xFT request normalizer should have returned a response object.
The test asserts the request to be valid. Verify the response contains the expected result.
✓ The request normalizer should not have returned an error.
✓ The request normalizer should have returned a result.
✓ The result JSON should match the expected control value.
xFT request normalizer unit test: options.startVector overridden with array string vertex ID:
✓ The xFT request normalizer should have returned a response object.
The test asserts the request to be valid. Verify the response contains the expected result.
✓ The request normalizer should not have returned an error.
✓ The request normalizer should have returned a result.
✓ The result JSON should match the expected control value.
xFT request normalizer unit test: Bad input: options.traverseContext set explicitly to wrong type:
✓ The xFT request normalizer should have returned a response object.
The test asserts the request to be invalid. Verify the response contains the expected error.
✓ The request normalizer should not have returned a result.
✓ The request normalizer should have returned an error string.
✓ The error string should match the expected control value.
xFT request normalizer unit test: options.traverseContext overridden explicitly:
✓ The xFT request normalizer should have returned a response object.
The test asserts the request to be valid. Verify the response contains the expected result.
✓ The request normalizer should not have returned an error.
✓ The request normalizer should have returned a result.
✓ The result JSON should match the expected control value.
xFT request normalizer unit test: Empty start vertex set with no options.allowEmptyStartVector override:
✓ The xFT request normalizer should have returned a response object.
The test asserts the request to be invalid. Verify the response contains the expected error.
✓ The request normalizer should not have returned a result.
✓ The request normalizer should have returned an error string.
✓ The error string should match the expected control value.
xFT request normalizer unit test: Empty start vertex with options.allowEmptyStartVector override set:
✓ The xFT request normalizer should have returned a response object.
The test asserts the request to be valid. Verify the response contains the expected result.
✓ The request normalizer should not have returned an error.
✓ The request normalizer should have returned a result.
✓ The result JSON should match the expected control value.
xFT visitor interface function unit test: Simple callback, no error, returns true.:
✓ xFT visitor method should have returned a response object.
✓ The call should not have returned an error.
✓ The call should have returned a result.
✓ The result should match the expected result.
✓ The flag indicating if a callback was executed should match expected result.
xFT visitor interface function unit test: Simple callback, no error, returns false.:
✓ xFT visitor method should have returned a response object.
✓ The call should not have returned an error.
✓ The call should have returned a result.
✓ The result should match the expected result.
✓ The flag indicating if a callback was executed should match expected result.
xFT visitor interface function unit test: Simple callback on undefined visitor method, no error.:
✓ xFT visitor method should have returned a response object.
✓ The call should not have returned an error.
✓ The call should have returned a result.
✓ The result should match the expected result.
✓ The flag indicating if a callback was executed should match expected result.
xFT visitor interface function unit test: Attempt to callback a visitor method that is not a function.:
✓ xFT visitor method should have returned a response object.
✓ The call not have returned a result.
✓ The call should have returned an error.
✓ The error should match the expected error string.
xFT visitor interface function unit test: Attempt to callback a visitor method that does not return a Boolean.:
✓ xFT visitor method should have returned a response object.
✓ The call not have returned a result.
✓ The call should have returned an error.
✓ The error should match the expected error string.
BFT test case: Missing request:
✓ The call to BFT should have returned a response object.
Test case is expected to fail. ensure the response error string is as expected.
✓ searchResponse.result should be null.
✓ searchResponse.error should be a non-null string.
✓ searchResponse.error string should match expected error string.
BFT test case: Bad request type:
✓ The call to BFT should have returned a response object.
Test case is expected to fail. ensure the response error string is as expected.
✓ searchResponse.result should be null.
✓ searchResponse.error should be a non-null string.
✓ searchResponse.error string should match expected error string.
BFT test case: Empty request:
✓ The call to BFT should have returned a response object.
Test case is expected to fail. ensure the response error string is as expected.
✓ searchResponse.result should be null.
✓ searchResponse.error should be a non-null string.
✓ searchResponse.error string should match expected error string.
BFT test case: Empty digraph:
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Single vertex, default starting vertex set:
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Single vertex, starting vertex not in the graph:
✓ The call to BFT should have returned a response object.
Test case is expected to fail. ensure the response error string is as expected.
✓ searchResponse.result should be null.
✓ searchResponse.error should be a non-null string.
✓ searchResponse.error string should match expected error string.
BFT test case: Single vertex, starting vertex specified explicity in request:
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Two disconnected vertices, default starting vertex set:
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Two disconnected vertices, starting vertex set set to 'islandA':
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Two disconnected vertices, starting vertex set set to 'islandB':
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Two connected vertices, default starting vertex set':
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Two connected vertices, starting vertex set set to 'islandA':
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Two connected vertices, starting vertex set set to 'islandB':
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Two connected vertices + a disconnected vertex w/default starting vertex set:
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Two connected vertices + a disconnected vertex w/default starting vertex set:
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Two vertices with a cycle w/default starting vertex set (which is the root vertex set of the digraph):
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Two vertices with a cycle w/default starting vertex set to 'A':
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Branch and then converge gray target tests:
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Branch and then converge black target tests:
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Hierarchy graph test A:
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Hiearchical graph test B (no start signal):
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Simple breadth-first search test w/default starting vertex set:
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
Breadth-first traverse termination tests.
BFT test case: Breadth-first visit terminate baseline (search not terminated):
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Breadth-first traverse terminate on 'initializeVertex':
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Breadth-first traverse terminate on 'startVertex':
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Breadth-first traverse terminate on 'discoverVertex':
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Breadth-first traverse terminate on 'examineVertex':
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Breadth-first traverse terminate on 'examineEdge':
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Breadth-first traverse terminate on 'treeEdge':
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Breadth-first traverse terminate on 'nonTreeEdge':
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Breadth-first traverse terminate on 'grayTarget':
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Breadth-first traverse terminate on 'blackTarget':
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
BFT test case: Breadth-first traverse terminate on 'finishVertex':
✓ The call to BFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
DFT test case: Missing request:
✓ The call to DFT should have returned a response object.
Test case is expected to fail. ensure the response error string is as expected.
✓ searchResponse.result should be null.
✓ searchResponse.error should be a non-null string.
✓ searchResponse.error string should match expected error string.
DFT test case: Bad request type:
✓ The call to DFT should have returned a response object.
Test case is expected to fail. ensure the response error string is as expected.
✓ searchResponse.result should be null.
✓ searchResponse.error should be a non-null string.
✓ searchResponse.error string should match expected error string.
DFT test case: Empty request:
✓ The call to DFT should have returned a response object.
Test case is expected to fail. ensure the response error string is as expected.
✓ searchResponse.result should be null.
✓ searchResponse.error should be a non-null string.
✓ searchResponse.error string should match expected error string.
DFT test case: Empty digraph:
✓ The call to DFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
DFT test case: Single vertex, default starting vertex set (initializeVertex, startVertex, discoverVertex, finishVertex test):
✓ The call to DFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
DFT test case: Single vertex, starting vertex not in the graph:
✓ The call to DFT should have returned a response object.
Test case is expected to fail. ensure the response error string is as expected.
✓ searchResponse.result should be null.
✓ searchResponse.error should be a non-null string.
✓ searchResponse.error string should match expected error string.
DFT test case: Single vertex, starting vertex specified explicity in request:
✓ The call to DFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
DFT test case: Single vertex, with an out-edge to itself:
✓ The call to DFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
DFT test case: Two connected vertices, (treeEdge test):
✓ The call to DFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
DFT test case: Two inter-connected vertices, (no starting vertex set):
✓ The call to DFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
DFT test case: Two inter-connected vertices, (backEdge test):
✓ The call to DFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
DFT test case: Three vertices, (forwardEdge test):
✓ The call to DFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
DFT test case: Three vertices (crossEdge test):
✓ The call to DFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
DFT test case: Intro to Algorithms Figure 23.4 path classification test:
✓ The call to DFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
Depth-first traverse termination tests.
DFT test case: Depth-first terminate on 'initializeVertex':
✓ The call to DFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
DFT test case: Depth-first terminate on 'startVertex':
✓ The call to DFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
DFT test case: Depth-first terminate on 'discoverVertex':
✓ The call to DFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
DFT test case: Depth-first terminate on 'examineEdge':
✓ The call to DFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
DFT test case: Depth-first terminate on 'treeEdge':
✓ The call to DFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
DFT test case: Depth-first terminate on 'treeEdge':
✓ The call to DFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
DFT test case: Depth-first terminate on 'backEdge':
✓ The call to DFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
DFT test case: Depth-first terminate on 'forwardOrCrossEdge':
✓ The call to DFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
DFT test case: Depth-first terminate on 'finishVertex':
✓ The call to DFT should have returned a response object.
Test case is expected to pass. analyze the search results and recorded traversal path.
✓ searchResponse.error should be null.
✓ searchResponse.result should match expected search response JSON.
✓ actualSearchPath should match the expected search path JSON.
Module export tests
Directed graph container API
✓ module export 'jsgraph.directed' should be an object
✓ module export 'jsgraph.directed.colors' should be an object
✓ module export 'jsgraph.directed.create' should be a function
✓ module export 'jsgraph.directed.transpose' should be a function
✓ module export 'jsgraph.directed.breadthFirstTraverse' should be a function
✓ module export 'jsgraph.directed.depthFirstTraverse' should be a function
✓ module export 'jsgraph.directed.createTraveralContext' should be a function
arc_core.types Test Suite:
Attempt to load the jbus-common-types-luts.
> loading module under test '../../BUILD/arccore/arc_core_types_luts'...
✓ The jbus-common-type-luts is expected to have loaded.
✓ The jbus-common-type-luts module is expected to export a static data table.
jbus common type converter test use case: Missing request object
✓ Type converter should have returned a response of type object.
✓ The request is expected to have failed.
✓ The response error should match the expected test control value.
jbus common type converter test use case: Null request object
✓ Type converter should have returned a response of type object.
✓ The request is expected to have failed.
✓ The response error should match the expected test control value.
jbus common type converter test use case: Invalid request object type
✓ Type converter should have returned a response of type object.
✓ The request is expected to have failed.
✓ The response error should match the expected test control value.
jbus common type converter test use case: Invalid request object: missing 'from'
✓ Type converter should have returned a response of type object.
✓ The request is expected to have failed.
✓ The response error should match the expected test control value.
jbus common type converter test use case: Invalid request object: 'from' is null
✓ Type converter should have returned a response of type object.
✓ The request is expected to have failed.
✓ The response error should match the expected test control value.
jbus common type converter test use case: Invalid request object: 'from' is undefined
✓ Type converter should have returned a response of type object.
✓ The request is expected to have failed.
✓ The response error should match the expected test control value.
jbus common type converter test use case: Invalid request object: 'from' is not a string
✓ Type converter should have returned a response of type object.
✓ The request is expected to have failed.
✓ The response error should match the expected test control value.
jbus common type converter test use case: Invalid request object: Missing 'to'
✓ Type converter should have returned a response of type object.
✓ The request is expected to have failed.
✓ The response error should match the expected test control value.
jbus common type converter test use case: Invalid request object: 'to' is null
✓ Type converter should have returned a response of type object.
✓ The request is expected to have failed.
✓ The response error should match the expected test control value.
jbus common type converter test use case: Invalid request object: 'to' is undefined
✓ Type converter should have returned a response of type object.
✓ The request is expected to have failed.
✓ The response error should match the expected test control value.
jbus common type converter test use case: Invalid request object: 'to' is not a string
✓ Type converter should have returned a response of type object.
✓ The request is expected to have failed.
✓ The response error should match the expected test control value.
jbus common type converter test use case: Invalid request object: Invalid 'from' string
✓ Type converter should have returned a response of type object.
✓ The request is expected to have failed.
✓ The response error should match the expected test control value.
jbus common type converter test use case: Invalid request object: Unity conversion doesn't make sense
✓ Type converter should have returned a response of type object.
✓ The request is expected to have failed.
✓ The response error should match the expected test control value.
jbus common type converter test use case: Invalid request object: Conversion from 'jsCode' with invalid value type.
✓ Type converter should have returned a response of type object.
✓ The request is expected to have failed.
✓ The response error should match the expected test control value.
jbus common type converter test use case: Invalid request object: Conversion from 'jsCode' with numerical value out-of-range.
✓ Type converter should have returned a response of type object.
✓ The request is expected to have failed.
✓ The response error should match the expected test control value.
jbus common type converter test use case: Invalid request object: Conversion of 'jsMoniker' to 'jsCode' w/'value' set to non-string.
✓ Type converter should have returned a response of type object.
✓ The request is expected to have failed.
✓ The response error should match the expected test control value.
jbus common type converter test use case: Invalid request object: Conversion of 'jsMoniker' to 'WTF_THIS'.
✓ Type converter should have returned a response of type object.
✓ The request is expected to have failed.
✓ The response error should match the expected test control value.
jbus common type converter test use case: Invalid request object: Conversion of 'jsMoniker' to 'jsCode' w/'value' set to bogus moniker value.
✓ Type converter should have returned a response of type object.
✓ The request is expected to have failed.
✓ The response error should match the expected test control value.
jbus common type converter test use case: Invalid request object: Conversion of 'jsMoniker' to 'jsCode' w/'value' set to bogus moniker value.
✓ Type converter should have returned a response of type object.
✓ The request is expected to have failed.
✓ The response error should match the expected test control value.
jbus common type converter test use case: Invalid request object: Conversion of 'jsReference' to 'jsMoniker' with invalid 'value'
✓ Type converter should have returned a response of type object.
✓ The request is expected to have failed.
✓ The response error should match the expected test control value.
jbus common type converter test use case: Invalid request: Convert a jsMoniker to jsonMoniker with value 'jsUndefined'
✓ Type converter should have returned a response of type object.
✓ The request is expected to have failed.
✓ The response error should match the expected test control value.
jbus common type converter test use case: Invalid request: Convert a jsMoniker to jsonMoniker with value 'jsFunction'
✓ Type converter should have returned a response of type object.
✓ The request is expected to have failed.
✓ The response error should match the expected test control value.
jbus common type converter test use case: Invlid request: Convert a jsReference to jsonMoniker with value function() {}
✓ Type converter should have returned a response of type object.
✓ The request is expected to have failed.
✓ The response error should match the expected test control value.
jbus common type converter test use case: Classify undefined reference with 'value' missing from request.
✓ Type converter should have returned a response of type object.
✓ The request is expected to have succeeded.
✓ The response result should match the expected test control value.
jbus common type converter test use case: Classify undefined reference with 'value' set to undefined.
✓ Type converter should have returned a response of type object.
✓ The request is expected to have succeeded.
✓ The response result should match the expected test control value.
jbus common type converter test use case: Classify undefined reference with 'value' set to null.
✓ Type converter should have returned a response of type object.
✓ The request is expected to have succeeded.
✓ The response result should match the expected test control value.
jbus common type converter test use case: Classify boolean reference with 'value' set to true.
✓ Type converter should have returned a response of type object.
✓ The request is expected to have succeeded.
✓ The response result should match the expected test control value.
jbus common type converter test use case: Classify string reference with 'value' set to 'test' string.
✓ Type converter should have returned a response of type object.
✓ The request is expected to have succeeded.
✓ The response result should match the expected test control value.
jbus common type converter test use case: Classify string reference with 'value' set to 17 number.
✓ Type converter should have returned a response of type object.
✓ The request is expected to have succeeded.
✓ The response result should match the expected test control value.
jbus common type converter test use case: Classify string reference with 'value' set to {} object.
✓ Type converter should have returned a response of type object.
✓ The request is expected to have succeeded.
✓ The response result should match the expected test control value.
jbus common type converter test use case: Classify string reference with 'value' set to [] array.
✓ Type converter should have returned a response of type object.
✓ The request is expected to have succeeded.
✓ The response result should match the expected test control value.
jbus common type converter test use case: Classify function reference with 'value' set to function.
✓ Type converter should have returned a response of type object.
✓ The request is expected to have succeeded.
✓ The response result should match the expected test control value.
jbus common type converter test use case: Convert a jsMoniker to jsonMoniker with value 'jsArray'
✓ Type converter should have returned a response of type object.
✓ The request is expected to have succeeded.
✓ The response result should match the expected test control value.
Attempt to load the jbus-common-types-check module.
✓ The jbus-common-types-check module is expected to have loaded.
✓ The module should export function 'inTypeSet'.
✓ The module should export function 'isJSON'.
Test 'types.inTypeSet' function.
jbus type 'inTypeSet' function test use case 'Missing request object.':
✓ The call to 'inTypeSet' should not have returned a result.
✓ The call to 'inTypeSet' should not have returned guidance.
✓ The call to 'inTypeSet' should have produced an error.
✓ The error reported by 'inTypeSet' should match expected string.
jbus type 'inTypeSet' function test use case 'Bad request type.':
✓ The call to 'inTypeSet' should not have returned a result.
✓ The call to 'inTypeSet' should not have returned guidance.
✓ The call to 'inTypeSet' should have produced an error.
✓ The error reported by 'inTypeSet' should match expected string.
jbus type 'inTypeSet' function test use case 'Empty request object.':
✓ The call to 'inTypeSet' should not have returned a result.
✓ The call to 'inTypeSet' should not have returned guidance.
✓ The call to 'inTypeSet' should have produced an error.
✓ The error reported by 'inTypeSet' should match expected string.
jbus type 'inTypeSet' function test use case 'Invalid request.types value (integer)':
✓ The call to 'inTypeSet' should not have returned a result.
✓ The call to 'inTypeSet' should not have returned guidance.
✓ The call to 'inTypeSet' should have produced an error.
✓ The error reported by 'inTypeSet' should match expected string.
jbus type 'inTypeSet' function test use case 'Valid request w/bogus type string as type set.':
✓ The call to 'inTypeSet' should not have returned an error.
✓ The call to 'inTypeSet' should have returned a result.
✓ The returned result should match expected result.
✓ The returned result guidance should match expected result.
jbus type 'inTypeSet' function test use case 'Valid request w/type not in type set (single jsMoniker).':
✓ The call to 'inTypeSet' should not have returned an error.
✓ The call to 'inTypeSet' should have returned a result.
✓ The returned result should match expected result.
✓ The returned result guidance should match expected result.
jbus type 'inTypeSet' function test use case 'Valid request w/type not in type set (array of jsMoniker).':
✓ The call to 'inTypeSet' should not have returned an error.
✓ The call to 'inTypeSet' should have returned a result.
✓ The returned result should match expected result.
✓ The returned result guidance should match expected result.
jbus type 'inTypeSet' function test use case 'Valid request w/type in type set (single jsMoniker).':
✓ The call to 'inTypeSet' should not have returned an error.
✓ The call to 'inTypeSet' should have returned a result.
✓ The returned result should match expected result.
✓ The returned result guidance should match expected result.
jbus type 'inTypeSet' function test use case 'Valid request/wtype in type set (array of jsMoniker).':
✓ The call to 'inTypeSet' should not have returned an error.
✓ The call to 'inTypeSet' should have returned a result.
✓ The returned result should match expected result.
✓ The returned result guidance should match expected result.
Test 'types.isJSON' function.
jbus type 'isJSON' function test use case 'Valid request (passing undefined).'.
✓ The call to 'isJSON' should not have returned an error.
✓ The call to 'isJSON' should have returned a result.
✓ The returned result should match expected result.
✓ The returned guidance should match expected result.
jbus type 'isJSON' function test use case 'Valid request (passing a function).'.
✓ The call to 'isJSON' should not have returned an error.
✓ The call to 'isJSON' should have returned a result.
✓ The returned result should match expected result.
✓ The returned guidance should match expected result.
jbus type 'isJSON' function test use case 'Valid request (null value).'.
✓ The call to 'isJSON' should not have returned an error.
✓ The call to 'isJSON' should have returned a result.
✓ The returned result should match expected result.
✓ The returned guidance should match expected result.
arc_core.identifier Test Suite:
jbus common IRUT generator test case: Bad input: Missing input.
✓ The call to fromReference should have returned a result object.
✓ The generator response.result should be null.
✓ The generator response.error should be a non-null string.
✓ The generator response.error string not be zero length.
✓ The error string should match control value.
jbus common IRUT generator test case: Empty object.
✓ The call to fromReference should have returned a result object.
✓ The generator should not have returned an error.
✓ The generator should have returned a result string.
✓ The result object should match control value.
✓ The result IRUT should be 22-characters in length.
jbus common IRUT generator test case: Empty object with an embedded function.
✓ The call to fromReference should have returned a result object.
✓ The generator should not have returned an error.
✓ The generator should have returned a result string.
✓ The result object should match control value.
✓ The result IRUT should be 22-characters in length.
jbus common IRUT generator test case: Empty object with an embedded function.
✓ The call to fromReference should have returned a result object.
✓ The generator should not have returned an error.
✓ The generator should have returned a result string.
✓ The result object should match control value.
✓ The result IRUT should be 22-characters in length.
jbus common IRUT generator test case: Simple object #1.
✓ The call to fromReference should have returned a result object.
✓ The generator should not have returned an error.
✓ The generator should have returned a result string.
✓ The result object should match control value.
✓ The result IRUT should be 22-characters in length.
jbus common IRUT generator test case: Basic test #1.
✓ The call to fromReference should have returned a result object.
✓ The generator should not have returned an error.
✓ The generator should have returned a result string.
✓ The result object should match control value.
✓ The result IRUT should be 22-characters in length.
jbus common IRUT generator test case: Hash an empty array.
✓ The call to fromReference should have returned a result object.
✓ The generator should not have returned an error.
✓ The generator should have returned a result string.
✓ The result object should match control value.
✓ The result IRUT should be 22-characters in length.
jbus common IRUT generator test case: Hash array with a single integer element 1.
✓ The call to fromReference should have returned a result object.
✓ The generator should not have returned an error.
✓ The generator should have returned a result string.
✓ The result object should match control value.
✓ The result IRUT should be 22-characters in length.
jbus common IRUT generator test case: Hash array with a single integer element 2.
✓ The call to fromReference should have returned a result object.
✓ The generator should not have returned an error.
✓ The generator should have returned a result string.
✓ The result object should match control value.
✓ The result IRUT should be 22-characters in length.
jbus common IRUT generator test case: Hash a bigger composite object.
✓ The call to fromReference should have returned a result object.
✓ The generator should not have returned an error.
✓ The generator should have returned a result string.
✓ The result object should match control value.
✓ The result IRUT should be 22-characters in length.
jbus common IRUT generator test case: Hash a bigger composite object (minor tweak - test hash stability).
✓ The call to fromReference should have returned a result object.
✓ The generator should not have returned an error.
✓ The generator should have returned a result string.
✓ The result object should match control value.
✓ The result IRUT should be 22-characters in length.
jbus common IRUT generator test case: Hash a big composite object way over the 64-character internal min key string size.
✓ The call to fromReference should have returned a result object.
✓ The generator should not have returned an error.
✓ The generator should have returned a result string.
✓ The result object should match control value.
✓ The result IRUT should be 22-characters in length.
jbus common IRUT generator test case: Hash a big composite object (touch the head).
✓ The call to fromReference should have returned a result object.
✓ The generator should not have returned an error.
✓ The generator should have returned a result string.
✓ The result object should match control value.
✓ The result IRUT should be 22-characters in length.
jbus common IRUT validator test case: Undefined request input.
✓ The call to isIRUT should have returned a result object.
✓ The validator should not have returned an error.
✓ The validator should have returned a non-null result.
✓ Response.result should match control value.
✓ Response.guidance should match control value.
jbus common IRUT validator test case: Invalid length string request input.
✓ The call to isIRUT should have returned a result object.
✓ The validator should not have returned an error.
✓ The validator should have returned a non-null result.
✓ Response.result should match control value.
✓ Response.guidance should match control value.
jbus common IRUT validator test case: Valid IRUT string 1 (A-V).
✓ The call to isIRUT should have returned a result object.
✓ The validator should not have returned an error.
✓ The validator should have returned a non-null result.
✓ Response.result should match control value.
✓ Response.guidance should match control value.
jbus common IRUT validator test case: Valid IRUT string 2 (W-r).
✓ The call to isIRUT should have returned a result object.
✓ The validator should not have returned an error.
✓ The validator should have returned a non-null result.
✓ Response.result should match control value.
✓ Response.guidance should match control value.
jbus common IRUT validator test case: Valid IRUT string 3 (s-_).
✓ The call to isIRUT should have returned a result object.
✓ The validator should not have returned an error.
✓ The validator should have returned a non-null result.
✓ Response.result should match control value.
✓ Response.guidance should match control value.
jbus common IRUT validator test case: Invalid IRUT (non-base64 char).
✓ The call to isIRUT should have returned a result object.
✓ The validator should not have returned an error.
✓ The validator should have returned a non-null result.
✓ Response.result should match control value.
✓ Response.guidance should match control value.
jbus common IRUT validator test case: Invalid IRUT (valid base64 but invalid IRUT char '+').
✓ The call to isIRUT should have returned a result object.
✓ The validator should not have returned an error.
✓ The validator should have returned a non-null result.
✓ Response.result should match control value.
✓ Response.guidance should match control value.
jbus common IRUT validator test case: Invalid IRUT (valid base64 but invalid IRUT char '/').
✓ The call to isIRUT should have returned a result object.
✓ The validator should not have returned an error.
✓ The validator should have returned a non-null result.
✓ Response.result should match control value.
✓ Response.guidance should match control value.
arc_core_.filter Test Suite:
arccore filter factory test use case: Bad input: missing request object
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Bad input: empty request object, missing operationID
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Bad input: operationID wrong type
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Bad input: operationID wrong type of string
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Bad input: operationID with invalid character
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Bad input: operationName wrong type.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have returned an error.
✓ The request should have returned a result.
✓ The request result is exepcted to be a NormalizedFunction instance.
Drill into the NormalizedFunction instance returned by createFilter.
✓ The NormalizedFunction instance should export function 'request'.
✓ The NormalizedFuction instance should export property 'filterDescriptor' of type object.
✓ The NormalizedFunction's request descriptor JSON should match control value.
arccore filter factory test use case: Bad input: operationDescription wrong type.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have returned an error.
✓ The request should have returned a result.
✓ The request result is exepcted to be a NormalizedFunction instance.
Drill into the NormalizedFunction instance returned by createFilter.
✓ The NormalizedFunction instance should export function 'request'.
✓ The NormalizedFuction instance should export property 'filterDescriptor' of type object.
✓ The NormalizedFunction's request descriptor JSON should match control value.
arccore filter factory test use case: Bad input: missing bodyFunction
✓ Filter.createFilter should have returned a response object.
✓ The request should not have returned an error.
✓ The request should have returned a result.
✓ The request result is exepcted to be a NormalizedFunction instance.
Drill into the NormalizedFunction instance returned by createFilter.
✓ The NormalizedFunction instance should export function 'request'.
✓ The NormalizedFuction instance should export property 'filterDescriptor' of type object.
✓ The NormalizedFunction's request descriptor JSON should match control value.
arccore filter factory test use case: Bad input: bodyFunction is wrong type
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: output map wrong type.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: empty output map object.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: input map wrong type.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: empty input map object.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: ____types wrong type.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: empty ____types unrecognized moniker value.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: empty ____types empty array.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: ____types array with unrecognized moniker.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: Invalid typemap directive.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: 1st rank valid, except subproperty is not an object.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: 1st rank valid, 2nd missing ____types.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: A larger example with multiple ranks with some errors.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: Invalid ____label type.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: Invalid ____description type.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: Invalid ____inValueSet constraint type.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: Invalid ____inRangeInclusive constraint type.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: Invalid ____inRangeInclusive constrain type 2.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: Invalid ____inRangeInclusive constrain type 3.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: A larger example with multiple ranks with some errors.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have returned an error.
✓ The request should have returned a result.
✓ The request result is exepcted to be a NormalizedFunction instance.
Drill into the NormalizedFunction instance returned by createFilter.
✓ The NormalizedFunction instance should export function 'request'.
✓ The NormalizedFuction instance should export property 'filterDescriptor' of type object.
✓ The NormalizedFunction's request descriptor JSON should match control value.
arccore filter factory test use case: Type map: test ____opaque type constraint.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have returned an error.
✓ The request should have returned a result.
✓ The request result is exepcted to be a NormalizedFunction instance.
Drill into the NormalizedFunction instance returned by createFilter.
✓ The NormalizedFunction instance should export function 'request'.
✓ The NormalizedFuction instance should export property 'filterDescriptor' of type object.
✓ The NormalizedFunction's request descriptor JSON should match control value.
arccore filter factory test use case: Type map: test ____opaque FALSE type constraint.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: test ____opaque and ____types (should fail).
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: test ____opaque and value-constrained directive (should fail).
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: test ____defaultValue declaration.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have returned an error.
✓ The request should have returned a result.
✓ The request result is exepcted to be a NormalizedFunction instance.
Drill into the NormalizedFunction instance returned by createFilter.
✓ The NormalizedFunction instance should export function 'request'.
✓ The NormalizedFuction instance should export property 'filterDescriptor' of type object.
✓ The NormalizedFunction's request descriptor JSON should match control value.
arccore filter factory test use case: Type map: test ____defaultValue declaration.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have returned an error.
✓ The request should have returned a result.
✓ The request result is exepcted to be a NormalizedFunction instance.
Drill into the NormalizedFunction instance returned by createFilter.
✓ The NormalizedFunction instance should export function 'request'.
✓ The NormalizedFuction instance should export property 'filterDescriptor' of type object.
✓ The NormalizedFunction's request descriptor JSON should match control value.
arccore filter factory test use case: Type map: test ____defaultValue with optional namespace.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: test ____defaultValue with opaque namespace.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have returned an error.
✓ The request should have returned a result.
✓ The request result is exepcted to be a NormalizedFunction instance.
Drill into the NormalizedFunction instance returned by createFilter.
✓ The NormalizedFunction instance should export function 'request'.
✓ The NormalizedFuction instance should export property 'filterDescriptor' of type object.
✓ The NormalizedFunction's request descriptor JSON should match control value.
arccore filter factory test use case: Type map: test ____accept with valid input.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have returned an error.
✓ The request should have returned a result.
✓ The request result is exepcted to be a NormalizedFunction instance.
Drill into the NormalizedFunction instance returned by createFilter.
✓ The NormalizedFunction instance should export function 'request'.
✓ The NormalizedFuction instance should export property 'filterDescriptor' of type object.
✓ The NormalizedFunction's request descriptor JSON should match control value.
arccore filter factory test use case: Type map: test ____accept with ____defaultValue.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have returned an error.
✓ The request should have returned a result.
✓ The request result is exepcted to be a NormalizedFunction instance.
Drill into the NormalizedFunction instance returned by createFilter.
✓ The NormalizedFunction instance should export function 'request'.
✓ The NormalizedFuction instance should export property 'filterDescriptor' of type object.
✓ The NormalizedFunction's request descriptor JSON should match control value.
arccore filter factory test use case: Type map: test ____accept with declared subnamespace.
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: test ____asMap directive (trivial case 1)
✓ Filter.createFilter should have returned a response object.
✓ The request should not have returned an error.
✓ The request should have returned a result.
✓ The request result is exepcted to be a NormalizedFunction instance.
Drill into the NormalizedFunction instance returned by createFilter.
✓ The NormalizedFunction instance should export function 'request'.
✓ The NormalizedFuction instance should export property 'filterDescriptor' of type object.
✓ The NormalizedFunction's request descriptor JSON should match control value.
arccore filter factory test use case: Type map: test ____asMap directive (missing subnamespace declaration)
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: test ____asMap directive (more than one subnamespace declared)
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: test ____appdsl directive (bad type)
✓ Filter.createFilter should have returned a response object.
✓ The request should not have produced a result.
✓ The request is expected to have produced an error.
✓ The request error is expected to match control value.
arccore filter factory test use case: Type map: test ____appdsl directive (valid)
✓ Filter.createFilter should have returned a response object.
✓ The request should not have returned an error.
✓ The request should have returned a result.
✓ The request result is exepcted to be a NormalizedFunction instance.
Drill into the NormalizedFunction instance returned by createFilter.
✓ The NormalizedFunction instance should export function 'request'.
✓ The NormalizedFuction instance should export property 'filterDescriptor' of type object.
✓ The NormalizedFunction's request descriptor JSON should match control value.
arccore filter factory test use case: Simple transform test 1
✓ Filter.createFilter should have returned a response object.
✓ The request should not have returned an error.
✓ The request should have returned a result.
✓ The request result is exepcted to be a NormalizedFunction instance.
Drill into the NormalizedFunction instance returned by createFilter.
✓ The NormalizedFunction instance should export function 'request'.
✓ The NormalizedFuction instance should export property 'filterDescriptor' of type object.
✓ The NormalizedFunction's request descriptor JSON should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Undefined request object':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned a result.
✓ Filter.runtime.filterRuntimeData should have returned an error.
✓ Filter.runtime.filterRuntimeData response.error should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Empty request object':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Request typemap is a string':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned a result.
✓ Filter.runtime.filterRuntimeData should have returned an error.
✓ Filter.runtime.filterRuntimeData response.error should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Request filterSpec is empty':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned a result.
✓ Filter.runtime.filterRuntimeData should have returned an error.
✓ Filter.runtime.filterRuntimeData response.error should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Request filterSpec specifies an undefined top-level type and undefined ioReference (implicitly)':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Request filterSpec specifies an undefined top-level type and undefined ioReference (explicitly)':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Request filterSpec specifies an null top-level type and an undefined ioReference (explicitly)':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned a result.
✓ Filter.runtime.filterRuntimeData should have returned an error.
✓ Filter.runtime.filterRuntimeData response.error should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Request filterSpec specifies a null top-level type and a null ioReference (explicitly)':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Request filterSpec specifies a null top-level type and a null ioReference (check the callback)':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Request filterSpec specifies an undefined top-level type and an undefined ioReference (check the callback)':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Attempt to pass a string through the filter.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Attempt to pass a number through the filter.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Attempt to pass a function through the filter.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Attempt to pass an object through the filter.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Attempt to pass an object w/subproperty through the filter.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Attempt to pass a populated object through an accept filter.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Attempt to pass a populated object through an accept filter.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Attempt to pass a populated array through an accept filter.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Advanced ____accept with ____defaultValue.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Advanced ____accept with ____defaultValue in a subnamespace of the request.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Advanced ____accept with ____defaultValue in a subnamespace of the request (with value).':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Boolean w/false default value, w/undefined input.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Boolean w/false default value, w/false input.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Boolean w/false default value, w/true input.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Boolean w/true default value, w/undefined input.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Boolean w/true default value, w/false input.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Boolean w/true default value, w/true input.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Object w/Boolean prop 'x' w/true default value, w/undefined 'x'.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Object w/Boolean prop 'x' w/true default value, w/false 'x'.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Object w/Boolean prop 'x' w/true default value, w/true 'x'.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Object w/numerical prop 'x' w/6 default value, w/undefined === 'x'.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Object w/numerical prop 'x' w/6 default value, w/0 === 'x'.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Object w/numerical prop 'x' w/true default value, w/true 'x'.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Object w/string prop 'x' w/'test' default value, w/''==='x'.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter.runtime.filterRuntimeData typemap test: 'Ensure that application-defined DSL metadata is ignored at runtime by filter.':
✓ Filter.runtime.filterRuntimeData have returned a response object.
✓ Filter.runtime.filterRuntimeData should not have returned an error.
✓ Filter.runtime.filterRuntimeData should have returned a result.
✓ Filter.runtime.filterRuntimeData's returned response.result should match control value.
Filter runtime use case: 'Filter runtime with bodyFunction that does not return a response object.':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Filter runtime bodyFunction explicitly returns an error.':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Filter runtime opaque input namespace test #1':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Filter runtime with mix of opaque, declared, and undeclared inputs.':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Filter runtime opaque namespace and default value (no request input case).':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Filter runtime opaque namespace and default value (with request input case).':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Filter runtime opaque namespace and default value advanced test 1.':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Filter runtime opaque namespace and default value (advanced case with no request input).':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Filter runtime opaque namespace and default value (advanced case with input case 1).':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Filter runtime opaque namespace and default value (advanced case with input case 2).':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Filter runtime top-level default value test #1 (no request)':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Filter runtime top-level default value test #2 (empty request object)':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Namespace 1 test 1':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Namespace 1 test 2':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Filter Namespace 2 missing request':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Filter Namespace 2 invalid request type':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Filter Namespace 2 empty request object':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Filter Namespace 2 request.y property wrong type':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Filter Namespace 2 request.y property valid value':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Advanced defaults triggers case #1':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Advanced defaults triggers case #2':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Advanced defaults triggers case #3':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Advanced defaults triggers case #4a':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Advanced defaults triggers case #4b':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Advanced defaults triggers case #4c':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Advanced defaults triggers case #4d (invalid input type)':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Advanced defaults triggers case #5a (request undefined -> should use default value)':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Advanced defaults triggers case #5b (request specifies outer object but not inner -> should use inner default)':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Advanced defaults triggers case #5c (request specifies outer object w/superflous subnamespaces but not inner namespace -> should use inner default)':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Advanced defaults triggers case #5d (request specifies outer object w/superflous subnamespaces but not inner namespace -> should use inner default)':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Advanced defaults triggers case #5e (invalid input type)':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Advanced defaults triggers case #6a (invalid undefined input)':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Advanced defaults triggers case #6b (outer object specified, inner object not specified -> should specify default value)':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Advanced defaults triggers case #6c (outer object specified, inner object specified -> should override default value)':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Advanced defaults triggers case #6d (invalid input type)':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Advanced defaults triggers case #7a (invalid undefined input)':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Advanced defaults triggers case #7b (outer object specified -> should specify default value)':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Advanced defaults triggers case #7c (outer object specified, inner object specified -> should override default value)':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Test runtime filter validation of an input map #1':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Test runtime filter validation of an input map #1 (w/bad element type)':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Test runtime filter validation of an input map #2':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Test missing request to base NF.request requiring object input.':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Test missing request to base NF.request w/opaque input.':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Unity transformation (passthrough input to output)':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Unity transformation (missing request)':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Filter I/O Test: Bogus request':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Filter I/O Test: Missing required inStringValueSetTest property':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Filter I/O Test: required inStringValueSetTest property is an invalid string value 'error'':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Filter I/O Test 1: Missing required inNumericalValueSetTest property':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Filter I/O Test: required inNumericalValueSetTest property is not a number':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Filter I/O Test: Missing required inStringRangeTest property':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Filter I/O Test: required inStringRangeTest property is not a string':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Filter I/O Test: required inStringRangeTest property is not a string':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Filter I/O Test: required inNumericalRangeTest property is not a string':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Filter I/O Test: Invalid array contents (wrong type of element value 1)':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Filter I/O Test: Invalid array contents (wrong type of element value 2)':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Filter I/O Test: inStringRangeTest property below range':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Filter I/O Test: inStringRangeTest above range':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'Filter I/O Test: inStringRangeTest in range':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
Filter runtime use case: 'Filter I/O Test: Invalid array contents (wrong type of element value)':
✓ Filter.request should have returned a response object.
✓ Filter.request call should not have returned a result.
✓ Filter.request call should have returned an error.
✓ Filter.request call response.error should match control value.
Filter runtime use case: 'No input or output typemap test.':
✓ Filter.request should have returned a response object.
✓ Filter.request call request should not have returned an error.
✓ Filter.request call should have returned a result.
✓ Filter.request call response.result should match control value.
ARC core type discriminator test suite.
Merged specification graph builder test suite:
ARC core type discriminator spec graph test use case: Empty filter array request.
✓ The spec graph builder should have returned a response object.
Verify expected valid result.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match control value.
✓ The result graph model is expected to have 1 vertices.
✓ The result graph model is expected to have 1 leaf vertices.
✓ The result graph model is expected to have 0 edges.
ARC core type discriminator spec graph test use case: Filter test1 by itself.
✓ The spec graph builder should have returned a response object.
Verify expected valid result.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match control value.
✓ The result graph model is expected to have 2 vertices.
✓ The result graph model is expected to have 1 leaf vertices.
✓ The result graph model is expected to have 1 edges.
ARC core type discriminator spec graph test use case: Filter test2 by itself.
✓ The spec graph builder should have returned a response object.
Verify expected valid result.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match control value.
✓ The result graph model is expected to have 3 vertices.
✓ The result graph model is expected to have 1 leaf vertices.
✓ The result graph model is expected to have 2 edges.
ARC core type discriminator spec graph test use case: Filter test3 by itself.
✓ The spec graph builder should have returned a response object.
Verify expected valid result.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match control value.
✓ The result graph model is expected to have 4 vertices.
✓ The result graph model is expected to have 2 leaf vertices.
✓ The result graph model is expected to have 3 edges.
ARC core type discriminator spec graph test use case: Filter test4 by itself.
✓ The spec graph builder should have returned a response object.
Verify expected valid result.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match control value.
✓ The result graph model is expected to have 4 vertices.
✓ The result graph model is expected to have 2 leaf vertices.
✓ The result graph model is expected to have 3 edges.
ARC core type discriminator spec graph test use case: Filter test5 by itself.
✓ The spec graph builder should have returned a response object.
Verify expected valid result.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match control value.
✓ The result graph model is expected to have 3 vertices.
✓ The result graph model is expected to have 1 leaf vertices.
✓ The result graph model is expected to have 2 edges.
ARC core type discriminator spec graph test use case: Filter test6 by itself.
✓ The spec graph builder should have returned a response object.
Verify expected valid result.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match control value.
✓ The result graph model is expected to have 2 vertices.
✓ The result graph model is expected to have 1 leaf vertices.
✓ The result graph model is expected to have 1 edges.
ARC core type discriminator spec graph test use case: Filter test7 by itself.
✓ The spec graph builder should have returned a response object.
Verify expected valid result.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match control value.
✓ The result graph model is expected to have 3 vertices.
✓ The result graph model is expected to have 2 leaf vertices.
✓ The result graph model is expected to have 2 edges.
ARC core type discriminator spec graph test use case: Filter test8 by itself.
✓ The spec graph builder should have returned a response object.
Verify expected valid result.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match control value.
✓ The result graph model is expected to have 4 vertices.
✓ The result graph model is expected to have 2 leaf vertices.
✓ The result graph model is expected to have 3 edges.
Ambiguity detector unit test suite:
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test1 filter by itself.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test2 filter by itself.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test3 filter by itself.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test4 filter by itself.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test5 filter by itself.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test6 filter by itself.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test7 filter by itself.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test8 filter by itself.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test1 + test2 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test1 + test3 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test1 + test4 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test1 + test5 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test1 + test6 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test1 + test7 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test1 + test8 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test2 + test3 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test2 + test4 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test2 + test5 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test2 + test6 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test2 + test7 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test2 + test8 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test3 + test4 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test3 + test5 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test3 + test6 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test3 + test7 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test3 + test8 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test4 + test5 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test4 + test6 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test4 + test7 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test4 + test8 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test5 + test6 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test5 + test7 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test5 + test8 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test6 + test7 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test6 + test8 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test7 + test8 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test1 + test2 + test3 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test1 + test2 + test4 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test1 + test2 + test5 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test1 + test2 + test6 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test1 + test2 + test7 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test1 + test2 + test8 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test2 + test3 + test4 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test2 + test3 + test5 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test2 + test3 + test6 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test2 + test3 + test7 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test2 + test3 + test8 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test3 + test4 + test5 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test3 + test4 + test6 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test3 + test4 + test7 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test3 + test4 + test8 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test4 + test5 + test6 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test4 + test5 + test7 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test4 + test5 + test8 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test5 + test6 + test7 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test5 + test6 + test8 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test1 + test2 + test3 + test4 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test1 + test2 + test3 + test5 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test1 + test2 + test3 + test6 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test1 + test2 + test3 + test7 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test1 + test2 + test3 + test8 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test1 + test2 + test3 + test4 + test5 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test1 + test2 + test3 + test4 + test6 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test1 + test2 + test3 + test4 + test7 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator ambiguity detector test use case: (test-type-discriminator-ambiguity-detector.js) test1 + test2 + test3 + test4 + test8 filters.:
✓ The ambiguity detector should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
Runtime parse model unit test suite:
ARC core type discriminator choice sets generator test use case: (test-type-discriminator-runtime-parse-digraph.js) Input Ambiguity Model #1:
✓ The choice sets generator should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator choice sets generator test use case: (test-type-discriminator-runtime-parse-digraph.js) Input Ambiguity Model #2:
✓ The choice sets generator should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator choice sets generator test use case: (test-type-discriminator-runtime-parse-digraph.js) Input Ambiguity Model #3:
✓ The choice sets generator should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
ARC core type discriminator choice sets generator test use case: (test-type-discriminator-runtime-parse-digraph.js) Input Ambiguity Model #4:
✓ The choice sets generator should have returned a response object.
Verify expected valid response.
✓ The request should not have returned an error.
✓ The request is expected to have returned a result object.
✓ The result object is expected to match the control value.
Discriminator Filter Factory unit test suite:
Filter [Request Discriminator Filter Factory:5A8uDJunQUm1w-HcBPQ6Gw] test '(test-type-discriminator-factory.js) Undefined Request':
Verify expected invalid result.
✓ The request should not have returned a result object.
✓ The request is expected to have produced an error.
✓ The error message is expected to match control value.
Filter [Request Discriminator Filter Factory:5A8uDJunQUm1w-HcBPQ6Gw] test '(test-type-discriminator-factory.js) Empty Request Object':
Verify expected invalid result.
✓ The request should not have returned a result object.
✓ The request is expected to have produced an error.
✓ The error message is expected to match control value.
Filter [Request Discriminator Filter Factory:5A8uDJunQUm1w-HcBPQ6Gw] test '(test-type-discriminator-factory.js) Empty Filters Array':
Verify expected invalid result.
✓ The request should not have returned a result object.
✓ The request is expected to have produced an error.
✓ The error message is expected to match control value.
Filter [Request Discriminator Filter Factory:5A8uDJunQUm1w-HcBPQ6Gw] test '(test-type-discriminator-factory.js) Simple Discriminator Test #1':
Verify expected valid result.
✓ The request should not have returned an error.
✓ The result object is expected to match control value.
Filter [Request Discriminator Filter Factory:5A8uDJunQUm1w-HcBPQ6Gw] test '(test-type-discriminator-factory.js) Simple Discriminator Test #2':
Verify expected valid result.
✓ The request should not have returned an error.
✓ The result object is expected to match control value.
Filter [Request Discriminator Filter Factory:5A8uDJunQUm1w-HcBPQ6Gw] test '(test-type-discriminator-factory.js) Simple Discriminator Test #3':
Verify expected valid result.
✓ The request should not have returned an error.
✓ The result object is expected to match control value.
Discriminator Filter runtime unit test suite:
Filter [Discriminator Filter:HnfY4Bk26YT-vsI4YL-giw] test 'Discriminator #1 w/string input.':
Verify expected valid result.
✓ The request should not have returned an error.
✓ The result object is expected to match control value.
Filter [Discriminator Filter:HnfY4Bk26YT-vsI4YL-giw] test 'Discriminator #1 w/object input.':
Verify expected valid result.
✓ The request should not have returned an error.
✓ The result object is expected to match control value.
Filter [Discriminator Filter:HnfY4Bk26YT-vsI4YL-giw] test 'Discriminator #1 w/object input + sub-property.':
Verify expected valid result.
✓ The request should not have returned an error.
✓ The result object is expected to match control value.
Filter [Discriminator Filter:HnfY4Bk26YT-vsI4YL-giw] test 'Discriminator #1 w/numerical input.':
Verify expected invalid result.
✓ The request should not have returned a result object.
✓ The request is expected to have produced an error.
✓ The error message is expected to match control value.
Filter [Discriminator Filter:irGy2m4xQJhFgPGmyeexmg] test 'Discriminator Color Hodge test #1':
Verify expected invalid result.
✓ The request should not have returned a result object.
✓ The request is expected to have produced an error.
✓ The error message is expected to match control value.
Filter [Discriminator Filter:irGy2m4xQJhFgPGmyeexmg] test 'Discriminator Color Hodge test #2':
Verify expected valid result.
✓ The request should not have returned an error.
✓ The result object is expected to match control value.
Filter [Discriminator Filter:irGy2m4xQJhFgPGmyeexmg] test 'Discriminator Color Hodge test #2A (get filter)':
Verify expected valid result.
✓ The request should not have returned an error.
✓ The result object is expected to match control value.
Filter [Discriminator Filter:irGy2m4xQJhFgPGmyeexmg] test 'Discriminator Color Hodge test #2A (route request)':
Verify expected invalid result.
✓ The request should not have returned a result object.
✓ The request is expected to have produced an error.
✓ The error message is expected to match control value.
Filter [Discriminator Filter:irGy2m4xQJhFgPGmyeexmg] test 'Discriminator Color Hodge test #2A (route request w/valid input data)':
Verify expected valid result.
✓ The request should not have returned an error.
✓ The result object is expected to match control value.
Filter [Discriminator Filter:irGy2m4xQJhFgPGmyeexmg] test 'Discriminator Color Hodge test #3':
Verify expected valid result.
✓ The request should not have returned an error.
✓ The result object is expected to match control value.
Filter [Discriminator Filter:irGy2m4xQJhFgPGmyeexmg] test 'Discriminator Color Hodge test #4':
Verify expected valid result.
✓ The request should not have returned an error.
✓ The result object is expected to match control value.
Filter [Discriminator Filter:irGy2m4xQJhFgPGmyeexmg] test 'Discriminator Color Hodge test #5':
Verify expected valid result.
✓ The request should not have returned an error.
✓ The result object is expected to match control value.
Filter [Discriminator Filter:irGy2m4xQJhFgPGmyeexmg] test 'Discriminator Color Hodge test #6':
Verify expected valid result.
✓ The request should not have returned an error.
✓ The result object is expected to match control value.
arc_core top-level package tests:
✓ The jbus-common module should have loaded.
arc_core.__bundle export namespace tests.
✓ arc_core.__bundle should be an object.
✓ arc_core.__bundle.murmurhash should be a function.
✓ arc_core.__bundle.nodeuuid should be a function.
arc_core.graph export namespace tests.
✓ arc_core.graph should be an object.
arc_core.identifier export namespace tests.
✓ arc_core_.identifier should be an object.
arc_core.identifier.hash export namespace tests.
✓ arc_core.identifier.hash should be an object.
✓ arc_core.identifier.murmur3.fromUTF8 should be a function.
✓ arc_core.identifier.murmur3.fromReference should be a function.
arc_core.identifier.irut export namespace tests.
✓ arc_core.identifier.irut should be an object.
✓ arc_core.identifier.irut.fromEther should be a function.
✓ arc_core.identifier.irut.fromReference should be a function.
✓ arc_core.identifier.irut.isIRUT should be a function.
arc_core.util export namespace tests.
✓ arc_core.util.util should be an object.
✓ util.clone should be a function.
✓ util.dictionaryLength should be a function.
✓ util.getEpochTime should a function.
arc_core.types export namespace tests.
✓ arc_core.types should be an object.
✓ arc_core.types.codes should be an object.
✓ arc_core.types.convert should be a function.
arc_core.types.check export namespace tests.
✓ types.check should be an object.
✓ arc_core.types.check.inTypeSet should be a function.
✓ arc_core.types.check.isJSON should be a function.
1855 passing (679ms)
[08:24:06] Finished 'test' after 2.74 s
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment