Failures:
test/Feature/AuthSpec.hs:88:7:
1) Feature.AuthSpec.authorization sql functions can read custom and standard claims variables
status mismatch:
expected: 200
but got: 400
body mismatch:
expected: [{"sub":"fun","nbf":1300819380,"iss":"joe","iat":1300819380,"http://postgrest.com/foo":true,"jti":"foo","exp":9999999999}]
but got: {"message":"invalid configuration parameter name \"request.jwt.claim.http://postgrest.com/foo\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.AuthSpec/authorization/sql functions can read custom and standard claims variables/"
test/Feature/CorsSpec.hs:72:27:
2) Feature.CorsSpec.CORS, postflight request, allows INFO body through even with CORS request headers present
predicate failed on: [("Content-Type","application/json; charset=utf-8")]
To rerun use: --match "/Feature.CorsSpec/CORS/postflight request/allows INFO body through even with CORS request headers present/"
test/Feature/InsertSpec.hs:137:11:
3) Feature.InsertSpec, Posting new record, from an html form, accepts disparate json types
status mismatch:
expected: 201
but got: 400
body mismatch:
expected: ""
but got: "{\"message\":\"invalid configuration parameter name \\\"request.header.content-type\\\"\",\"code\":\"42602\",\"details\":\"Custom parameter names must be two or more simple identifiers separated by dots.\",\"hint\":null}"
To rerun use: --match "/Feature.InsertSpec/Posting new record/from an html form/accepts disparate json types/"
test/Feature/InsertSpec.hs:398:11:
4) Feature.InsertSpec, CSV insert, requesting full representation, returns full details of inserted record
status mismatch:
expected: 201
but got: 400
missing header:
Content-Type: text/csv; charset=utf-8
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: "a,b\nbar,baz"
but got: "{\"message\":\"invalid configuration parameter name \\\"request.header.content-type\\\"\",\"code\":\"42602\",\"details\":\"Custom parameter names must be two or more simple identifiers separated by dots.\",\"hint\":null}"
To rerun use: --match "/Feature.InsertSpec/CSV insert/requesting full representation/returns full details of inserted record/"
test/Feature/InsertSpec.hs:407:11:
5) Feature.InsertSpec, CSV insert, requesting full representation, can post nulls
status mismatch:
expected: 201
but got: 400
missing header:
Content-Type: text/csv; charset=utf-8
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: "a,b\n,foo"
but got: "{\"message\":\"invalid configuration parameter name \\\"request.header.content-type\\\"\",\"code\":\"42602\",\"details\":\"Custom parameter names must be two or more simple identifiers separated by dots.\",\"hint\":null}"
To rerun use: --match "/Feature.InsertSpec/CSV insert/requesting full representation/can post nulls/"
test/Feature/InsertSpec.hs:416:11:
6) Feature.InsertSpec, CSV insert, requesting full representation, only returns the requested column header with its associated data
status mismatch:
expected: 201
but got: 400
missing header:
Content-Type: text/csv; charset=utf-8
missing header:
Content-Range: */*
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: "id\n8\n9"
but got: "{\"message\":\"invalid configuration parameter name \\\"request.header.content-type\\\"\",\"code\":\"42602\",\"details\":\"Custom parameter names must be two or more simple identifiers separated by dots.\",\"hint\":null}"
To rerun use: --match "/Feature.InsertSpec/CSV insert/requesting full representation/only returns the requested column header with its associated data/"
test/Feature/RpcSpec.hs:29:12:
7) Feature.RpcSpec, remote procedure call, a proc that returns a set, returns paginated results
status mismatch:
expected: 200
but got: 400
missing header:
Content-Range: 0-0/*
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: [{"id":3}]
but got: {"message":"invalid configuration parameter name \"request.header.range-unit\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.RpcSpec/remote procedure call/a proc that returns a set/returns paginated results/"
test/Feature/RpcSpec.hs:50:12:
8) Feature.RpcSpec, remote procedure call, a proc that returns a set, includes total count if requested
status mismatch:
expected: 206
but got: 400
missing header:
Content-Range: 0-0/2
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: [{"id":3}]
but got: {"message":"invalid configuration parameter name \"request.header.range-unit\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.RpcSpec/remote procedure call/a proc that returns a set/includes total count if requested/"
test/Feature/RpcSpec.hs:438:11:
9) Feature.RpcSpec, remote procedure call, proc argument types, accepts a variety of arguments from an html form
status mismatch:
expected: 200
but got: 400
body mismatch:
expected: {"boolean":true,"varchar":"hello","date":"2019-01-01","integer":43,"arr":["a","b","c"],"jsonb":{},"money":"$0.00","double":3.1,"json":{},"enum":"foo"}
but got: {"message":"invalid configuration parameter name \"request.header.content-type\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.RpcSpec/remote procedure call/proc argument types/accepts a variety of arguments from an html form/"
test/Feature/RpcSpec.hs:610:15:
10) Feature.RpcSpec, remote procedure call, procs with VARIADIC params, works with POST and repeated params from html form, n=0 (through DEFAULT)
status mismatch:
expected: 200
but got: 400
body mismatch:
expected: []
but got: {"message":"invalid configuration parameter name \"request.header.content-type\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.RpcSpec/remote procedure call/procs with VARIADIC params/works with POST and repeated params from html form/n=0 (through DEFAULT)/"
test/Feature/RpcSpec.hs:617:15:
11) Feature.RpcSpec, remote procedure call, procs with VARIADIC params, works with POST and repeated params from html form, n=1
status mismatch:
expected: 200
but got: 400
body mismatch:
expected: ["hi"]
but got: {"message":"invalid configuration parameter name \"request.header.content-type\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.RpcSpec/remote procedure call/procs with VARIADIC params/works with POST and repeated params from html form/n=1/"
test/Feature/RpcSpec.hs:624:15:
12) Feature.RpcSpec, remote procedure call, procs with VARIADIC params, works with POST and repeated params from html form, n>1
status mismatch:
expected: 200
but got: 400
body mismatch:
expected: ["hi","there"]
but got: {"message":"invalid configuration parameter name \"request.header.content-type\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.RpcSpec/remote procedure call/procs with VARIADIC params/works with POST and repeated params from html form/n>1/"
test/Feature/RpcSpec.hs:672:66:
13) Feature.RpcSpec, remote procedure call, expects a single json object, accepts parameters from an html form
status mismatch:
expected: 200
but got: 400
body mismatch:
expected: {"boolean":"false","varchar":"forms are fun","date":"1900-01-01","integer":"7","money":"$3.99","double":"2.71828","enum":"foo"}
but got: {"message":"invalid configuration parameter name \"request.header.content-type\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.RpcSpec/remote procedure call/expects a single json object/accepts parameters from an html form/"
test/Feature/RpcSpec.hs:705:11:
14) Feature.RpcSpec, remote procedure call, should work with an overloaded function, overloaded_html_form()
status mismatch:
expected: 200
but got: 400
body mismatch:
expected: [1,2,3]
but got: {"message":"invalid configuration parameter name \"request.header.content-type\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.RpcSpec/remote procedure call/should work with an overloaded function/overloaded_html_form()/"
test/Feature/RpcSpec.hs:712:11:
15) Feature.RpcSpec, remote procedure call, should work with an overloaded function, overloaded_html_form(json) single-object
status mismatch:
expected: 200
but got: 400
body mismatch:
expected: {"a":"1","b":"2","c":"3"}
but got: {"message":"invalid configuration parameter name \"request.header.content-type\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.RpcSpec/remote procedure call/should work with an overloaded function/overloaded_html_form(json) single-object/"
test/Feature/RpcSpec.hs:719:11:
16) Feature.RpcSpec, remote procedure call, should work with an overloaded function, overloaded_html_form(int, int)
status mismatch:
expected: 200
but got: 400
body mismatch:
expected: 3
but got: {"message":"invalid configuration parameter name \"request.header.content-type\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.RpcSpec/remote procedure call/should work with an overloaded function/overloaded_html_form(int, int)/"
test/Feature/RpcSpec.hs:726:11:
17) Feature.RpcSpec, remote procedure call, should work with an overloaded function, overloaded_html_form(text, text, text)
status mismatch:
expected: 200
but got: 400
body mismatch:
expected: "123"
but got: {"message":"invalid configuration parameter name \"request.header.content-type\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.RpcSpec/remote procedure call/should work with an overloaded function/overloaded_html_form(text, text, text)/"
test/Feature/RpcSpec.hs:764:11:
18) Feature.RpcSpec, remote procedure call, bulk RPC with params=multiple-objects, works with a scalar function an returns a json array when posting CSV
status mismatch:
expected: 200
but got: 400
body mismatch:
expected: [3,10,300]
but got: {"message":"invalid configuration parameter name \"request.header.content-type\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.RpcSpec/remote procedure call/bulk RPC with params=multiple-objects/works with a scalar function an returns a json array when posting CSV/"
test/Feature/RpcSpec.hs:790:13:
19) Feature.RpcSpec, remote procedure call, HTTP request env vars, custom header is set
status mismatch:
expected: 200
but got: 400
body mismatch:
expected: "test"
but got: {"message":"invalid configuration parameter name \"request.header.custom-header\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.RpcSpec/remote procedure call/HTTP request env vars/custom header is set/"
test/Feature/RangeSpec.hs:48:29:
20) Feature.RangeSpec, POST /rpc/getitemrange, with range headers, of acceptable range, succeeds with partial content
predicate failed on: [("Content-Type","application/json; charset=utf-8")]
To rerun use: --match "/Feature.RangeSpec/POST /rpc/getitemrange/with range headers/of acceptable range/succeeds with partial content/"
test/Feature/RangeSpec.hs:55:13:
21) Feature.RangeSpec, POST /rpc/getitemrange, with range headers, of acceptable range, understands open-ended ranges
status mismatch:
expected: 200
but got: 400
To rerun use: --match "/Feature.RangeSpec/POST /rpc/getitemrange/with range headers/of acceptable range/understands open-ended ranges/"
test/Feature/RangeSpec.hs:60:13:
22) Feature.RangeSpec, POST /rpc/getitemrange, with range headers, of acceptable range, returns an empty body when there are no results
status mismatch:
expected: 200
but got: 400
missing header:
Content-Range: */*
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: []
but got: {"message":"invalid configuration parameter name \"request.header.range-unit\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.RangeSpec/POST /rpc/getitemrange/with range headers/of acceptable range/returns an empty body when there are no results/"
test/Feature/RangeSpec.hs:69:29:
23) Feature.RangeSpec, POST /rpc/getitemrange, with range headers, of acceptable range, allows one-item requests
predicate failed on: [("Content-Type","application/json; charset=utf-8")]
To rerun use: --match "/Feature.RangeSpec/POST /rpc/getitemrange/with range headers/of acceptable range/allows one-item requests/"
test/Feature/RangeSpec.hs:77:29:
24) Feature.RangeSpec, POST /rpc/getitemrange, with range headers, of acceptable range, handles ranges beyond collection length via truncation
predicate failed on: [("Content-Type","application/json; charset=utf-8")]
To rerun use: --match "/Feature.RangeSpec/POST /rpc/getitemrange/with range headers/of acceptable range/handles ranges beyond collection length via truncation/"
test/Feature/RangeSpec.hs:90:13:
25) Feature.RangeSpec, POST /rpc/getitemrange, with range headers, of invalid range, refuses a range with nonzero start when there are no items
status mismatch:
expected: 416
but got: 400
missing header:
Content-Range: */0
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: []
but got: {"message":"invalid configuration parameter name \"request.header.range-unit\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.RangeSpec/POST /rpc/getitemrange/with range headers/of invalid range/refuses a range with nonzero start when there are no items/"
test/Feature/RangeSpec.hs:98:13:
26) Feature.RangeSpec, POST /rpc/getitemrange, with range headers, of invalid range, refuses a range requesting start past last item
status mismatch:
expected: 416
but got: 400
missing header:
Content-Range: */15
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: []
but got: {"message":"invalid configuration parameter name \"request.header.range-unit\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.RangeSpec/POST /rpc/getitemrange/with range headers/of invalid range/refuses a range requesting start past last item/"
test/Feature/RangeSpec.hs:147:11:
27) Feature.RangeSpec, GET /items, with limit/offset parameters, headers override get parameters
status mismatch:
expected: 200
but got: 400
missing header:
Content-Range: 0-1/*
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: [{"id":1},{"id":2}]
but got: {"message":"invalid configuration parameter name \"request.header.range-unit\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.RangeSpec/GET /items/with limit/offset parameters/headers override get parameters/"
test/Feature/RangeSpec.hs:299:29:
28) Feature.RangeSpec, GET /items, with range headers, of acceptable range, succeeds with partial content
predicate failed on: [("Content-Type","application/json; charset=utf-8")]
To rerun use: --match "/Feature.RangeSpec/GET /items/with range headers/of acceptable range/succeeds with partial content/"
test/Feature/RangeSpec.hs:306:13:
29) Feature.RangeSpec, GET /items, with range headers, of acceptable range, understands open-ended ranges
status mismatch:
expected: 200
but got: 400
To rerun use: --match "/Feature.RangeSpec/GET /items/with range headers/of acceptable range/understands open-ended ranges/"
test/Feature/RangeSpec.hs:311:13:
30) Feature.RangeSpec, GET /items, with range headers, of acceptable range, returns an empty body when there are no results
status mismatch:
expected: 200
but got: 400
missing header:
Content-Range: */*
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: []
but got: {"message":"invalid configuration parameter name \"request.header.range-unit\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.RangeSpec/GET /items/with range headers/of acceptable range/returns an empty body when there are no results/"
test/Feature/RangeSpec.hs:320:29:
31) Feature.RangeSpec, GET /items, with range headers, of acceptable range, allows one-item requests
predicate failed on: [("Content-Type","application/json; charset=utf-8")]
To rerun use: --match "/Feature.RangeSpec/GET /items/with range headers/of acceptable range/allows one-item requests/"
test/Feature/RangeSpec.hs:328:29:
32) Feature.RangeSpec, GET /items, with range headers, of acceptable range, handles ranges beyond collection length via truncation
predicate failed on: [("Content-Type","application/json; charset=utf-8")]
To rerun use: --match "/Feature.RangeSpec/GET /items/with range headers/of acceptable range/handles ranges beyond collection length via truncation/"
test/Feature/RangeSpec.hs:341:13:
33) Feature.RangeSpec, GET /items, with range headers, of invalid range, refuses a range with nonzero start when there are no items
status mismatch:
expected: 416
but got: 400
missing header:
Content-Range: */0
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: []
but got: {"message":"invalid configuration parameter name \"request.header.range-unit\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.RangeSpec/GET /items/with range headers/of invalid range/refuses a range with nonzero start when there are no items/"
test/Feature/RangeSpec.hs:349:13:
34) Feature.RangeSpec, GET /items, with range headers, of invalid range, refuses a range requesting start past last item
status mismatch:
expected: 416
but got: 400
missing header:
Content-Range: */15
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: []
but got: {"message":"invalid configuration parameter name \"request.header.range-unit\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.RangeSpec/GET /items/with range headers/of invalid range/refuses a range requesting start past last item/"
test/Feature/QueryLimitedSpec.hs:26:9:
35) Feature.QueryLimitedSpec, Requesting many items with server limits(max-rows) enabled, respects additional client limiting
status mismatch:
expected: 200
but got: 400
missing header:
Content-Range: 0-0/*
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: [{"id":1}]
but got: {"message":"invalid configuration parameter name \"request.header.range-unit\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.QueryLimitedSpec/Requesting many items with server limits(max-rows) enabled/respects additional client limiting/"
test/Feature/IgnorePrivOpenApiSpec.hs:44:26:
36) Feature.IgnorePrivOpenApiSpec, OpenAPI Ignore Privileges, table, only includes tables that belong to another schema if the Accept-Profile header is used
not expected: Nothing
To rerun use: --match "/Feature.IgnorePrivOpenApiSpec/OpenAPI Ignore Privileges/table/only includes tables that belong to another schema if the Accept-Profile header is used/"
test/Feature/IgnorePrivOpenApiSpec.hs:76:25:
37) Feature.IgnorePrivOpenApiSpec, OpenAPI Ignore Privileges, RPC, only includes functions that belong to another schema if the Accept-Profile header is used
not expected: Nothing
To rerun use: --match "/Feature.IgnorePrivOpenApiSpec/OpenAPI Ignore Privileges/RPC/only includes functions that belong to another schema if the Accept-Profile header is used/"
test/Feature/RpcPreRequestGucsSpec.hs:27:9:
38) Feature.RpcPreRequestGucsSpec, GUC headers on all methods via pre-request, succeeds setting the headers on GET and HEAD
status mismatch:
expected: 200
but got: 400
missing header:
Cache-Control: no-cache, no-store, must-revalidate
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: [{"id":1}]
but got: {"message":"invalid configuration parameter name \"request.header.user-agent\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.RpcPreRequestGucsSpec/GUC headers on all methods via pre-request/succeeds setting the headers on GET and HEAD/"
test/Feature/MultipleSchemaSpec.hs:36:68:
39) Feature.MultipleSchemaSpec, multiple schemas in single instance, Reading tables on different schemas, succeeds in reading table from default schema v1 after explicitly passing it in the header
status mismatch:
expected: 200
but got: 400
missing header:
Content-Profile: v1
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: [{"name":"parent v1-1","id":1},{"name":"parent v1-2","id":2}]
but got: {"message":"invalid configuration parameter name \"request.header.accept-profile\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.MultipleSchemaSpec/multiple schemas in single instance/Reading tables on different schemas/succeeds in reading table from default schema v1 after explicitly passing it in the header/"
test/Feature/MultipleSchemaSpec.hs:47:68:
40) Feature.MultipleSchemaSpec, multiple schemas in single instance, Reading tables on different schemas, succeeds in reading table from schema v2
status mismatch:
expected: 200
but got: 400
missing header:
Content-Profile: v2
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: [{"name":"parent v2-3","id":3},{"name":"parent v2-4","id":4}]
but got: {"message":"invalid configuration parameter name \"request.header.accept-profile\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.MultipleSchemaSpec/multiple schemas in single instance/Reading tables on different schemas/succeeds in reading table from schema v2/"
test/Feature/MultipleSchemaSpec.hs:58:74:
41) Feature.MultipleSchemaSpec, multiple schemas in single instance, Reading tables on different schemas, succeeds in reading another_table from schema v2
status mismatch:
expected: 200
but got: 400
missing header:
Content-Profile: v2
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: [{"id":5,"another_value":"value 5"},{"id":6,"another_value":"value 6"}]
but got: {"message":"invalid configuration parameter name \"request.header.accept-profile\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.MultipleSchemaSpec/multiple schemas in single instance/Reading tables on different schemas/succeeds in reading another_table from schema v2/"
test/Feature/MultipleSchemaSpec.hs:69:74:
42) Feature.MultipleSchemaSpec, multiple schemas in single instance, Reading tables on different schemas, doesn't find another_table in schema v1
status mismatch:
expected: 404
but got: 400
To rerun use: --match "/Feature.MultipleSchemaSpec/multiple schemas in single instance/Reading tables on different schemas/doesn't find another_table in schema v1/"
test/Feature/MultipleSchemaSpec.hs:94:11:
43) Feature.MultipleSchemaSpec, multiple schemas in single instance, Inserting tables on different schemas, succeeds inserting on the v1 schema and returning its parent
status mismatch:
expected: 201
but got: 400
missing header:
Content-Profile: v1
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: [{"id":0,"parent":{"name":"parent v1-2","id":2}}]
but got: {"message":"invalid configuration parameter name \"request.header.content-profile\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.MultipleSchemaSpec/multiple schemas in single instance/Inserting tables on different schemas/succeeds inserting on the v1 schema and returning its parent/"
test/Feature/MultipleSchemaSpec.hs:105:11:
44) Feature.MultipleSchemaSpec, multiple schemas in single instance, Inserting tables on different schemas, succeeds inserting on the v2 schema and returning its parent
status mismatch:
expected: 201
but got: 400
missing header:
Content-Profile: v2
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: [{"id":0,"parent":{"name":"parent v2-3","id":3}}]
but got: {"message":"invalid configuration parameter name \"request.header.content-profile\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.MultipleSchemaSpec/multiple schemas in single instance/Inserting tables on different schemas/succeeds inserting on the v2 schema and returning its parent/"
test/Feature/MultipleSchemaSpec.hs:133:11:
45) Feature.MultipleSchemaSpec, multiple schemas in single instance, calling procs on different schemas, succeeds in calling the v1 schema proc and embedding
status mismatch:
expected: 200
but got: 400
missing header:
Content-Profile: v1
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: [{"name":"parent v1-1","id":1,"children":[{"name":"child v1-1","id":1}]},{"name":"parent v1-2","id":2,"children":[{"name":"child v1-2","id":2}]}]
but got: {"message":"invalid configuration parameter name \"request.header.accept-profile\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.MultipleSchemaSpec/multiple schemas in single instance/calling procs on different schemas/succeeds in calling the v1 schema proc and embedding/"
test/Feature/MultipleSchemaSpec.hs:144:11:
46) Feature.MultipleSchemaSpec, multiple schemas in single instance, calling procs on different schemas, succeeds in calling the v2 schema proc and embedding
status mismatch:
expected: 200
but got: 400
missing header:
Content-Profile: v2
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: [{"name":"parent v2-3","id":3,"children":[{"name":"child v2-3","id":1}]},{"name":"parent v2-4","id":4,"children":[]}]
but got: {"message":"invalid configuration parameter name \"request.header.accept-profile\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.MultipleSchemaSpec/multiple schemas in single instance/calling procs on different schemas/succeeds in calling the v2 schema proc and embedding/"
test/Feature/MultipleSchemaSpec.hs:156:11:
47) Feature.MultipleSchemaSpec, multiple schemas in single instance, calling procs on different schemas, succeeds in calling the v2 schema proc with POST by using Content-Profile
status mismatch:
expected: 200
but got: 400
missing header:
Content-Profile: v2
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: [{"name":"parent v2-3","id":3},{"name":"parent v2-4","id":4}]
but got: {"message":"invalid configuration parameter name \"request.header.content-profile\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.MultipleSchemaSpec/multiple schemas in single instance/calling procs on different schemas/succeeds in calling the v2 schema proc with POST by using Content-Profile/"
test/Feature/MultipleSchemaSpec.hs:169:11:
48) Feature.MultipleSchemaSpec, multiple schemas in single instance, Modifying tables on different schemas, succeeds in patching on the v1 schema and returning its parent
status mismatch:
expected: 200
but got: 400
missing header:
Content-Profile: v1
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: [{"name":"child v1-1 updated","parent":{"name":"parent v1-1"}}]
but got: {"message":"invalid configuration parameter name \"request.header.content-profile\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.MultipleSchemaSpec/multiple schemas in single instance/Modifying tables on different schemas/succeeds in patching on the v1 schema and returning its parent/"
test/Feature/MultipleSchemaSpec.hs:179:11:
49) Feature.MultipleSchemaSpec, multiple schemas in single instance, Modifying tables on different schemas, succeeds in patching on the v2 schema and returning its parent
status mismatch:
expected: 200
but got: 400
missing header:
Content-Profile: v2
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: [{"name":"child v2-1 updated","parent":{"name":"parent v2-3"}}]
but got: {"message":"invalid configuration parameter name \"request.header.content-profile\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.MultipleSchemaSpec/multiple schemas in single instance/Modifying tables on different schemas/succeeds in patching on the v2 schema and returning its parent/"
test/Feature/MultipleSchemaSpec.hs:190:11:
50) Feature.MultipleSchemaSpec, multiple schemas in single instance, Modifying tables on different schemas, succeeds on deleting on the v2 schema
status mismatch:
expected: 200
but got: 400
missing header:
Content-Profile: v2
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: [{"name":"child v2-3","id":1,"parent_id":3}]
but got: {"message":"invalid configuration parameter name \"request.header.content-profile\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.MultipleSchemaSpec/multiple schemas in single instance/Modifying tables on different schemas/succeeds on deleting on the v2 schema/"
test/Feature/MultipleSchemaSpec.hs:198:13:
51) Feature.MultipleSchemaSpec, multiple schemas in single instance, Modifying tables on different schemas, succeeds on PUT on the v2 schema
status mismatch:
expected: 200
but got: 400
missing header:
Content-Profile: v2
the actual headers were:
Content-Type: application/json; charset=utf-8
body mismatch:
expected: [{"name":"child v2-111","id":111,"parent_id":null}]
but got: {"message":"invalid configuration parameter name \"request.header.content-profile\"","code":"42602","details":"Custom parameter names must be two or more simple identifiers separated by dots.","hint":null}
To rerun use: --match "/Feature.MultipleSchemaSpec/multiple schemas in single instance/Modifying tables on different schemas/succeeds on PUT on the v2 schema/"
test/Feature/MultipleSchemaSpec.hs:239:29:
52) Feature.MultipleSchemaSpec, multiple schemas in single instance, OpenAPI output, succeeds in reading table definition from default schema v1 after explicitly passing it in the header
predicate failed on: [("Content-Type","application/json; charset=utf-8")]
To rerun use: --match "/Feature.MultipleSchemaSpec/multiple schemas in single instance/OpenAPI output/succeeds in reading table definition from default schema v1 after explicitly passing it in the header/"
test/Feature/MultipleSchemaSpec.hs:268:29:
53) Feature.MultipleSchemaSpec, multiple schemas in single instance, OpenAPI output, succeeds in reading table definition from schema v2
predicate failed on: [("Content-Type","application/json; charset=utf-8")]
To rerun use: --match "/Feature.MultipleSchemaSpec/multiple schemas in single instance/OpenAPI output/succeeds in reading table definition from schema v2/"
test/Feature/MultipleSchemaSpec.hs:297:29:
54) Feature.MultipleSchemaSpec, multiple schemas in single instance, OpenAPI output, succeeds in reading another_table definition from schema v2
predicate failed on: [("Content-Type","application/json; charset=utf-8")]
To rerun use: --match "/Feature.MultipleSchemaSpec/multiple schemas in single instance/OpenAPI output/succeeds in reading another_table definition from schema v2/"
Randomized with seed 855754588
Finished in 6.8972 seconds
737 examples, 54 failures, 1 pending
Test suite spec: FAIL
Test suite logged to: dist/test/postgrest-8.0.0-spec.log
1 of 2 test suites (1 of 2 test cases) passed.
felixonmars
commented
2 years ago
Environment
Description of issue
Run test suite of postgrest.