pgtap
pgtap copied to clipboard
theory
PostgreSQL Unit Testing Suite
This affects the function tests (IE: function_owner_is), but might impact others. The current API of passing in a name is problematic because if you pass in a non-canonical type name...
This is a similar issue to #24, but my query is about using runtests and a simple naming scheme/pattern to invoke test fixtures on a _per test case_ basis. I'll...
Currently, we have two versions of a bunch of functions, one that takes a schema and an object, and another that just takes the object. We should add a variant...
`has_check()` is currently quite limited. It should be updated to have the same interface as `has_index()`.
The `has_operator()`, `has_leftop()`, and `has_rightop()` functions do not allow schema names to be passed for the type parameters. I think it makes sense to just let them be included in...
Instead of requiring that the schema, function name, and array of param types be passed separately, consider adding alternate functions for the function-testing assertions that accept a `regprocedure` parameter. Would...
Useful result testing function to consider adding (but might require C code): `rowtype_is()`. Could certainly simplify the diagnostic output of `results_eq()` when the values are the same but the types...
Useful schema testing functions to consider adding: - `sequence_has_range()` - `sequence_increments_by()` - `sequence_starts_at()` - `sequence_cycles()`
Add variants of `set_eq()`, `bag_eq()`, and `results_eq()` that take an array of records as the second argument Probably would require C code.