You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
utPLSQL expectations incorporates advanced data comparison options when comparing compound data-types:
@@ -6,7 +8,7 @@ utPLSQL expectations incorporates advanced data comparison options when comparin
6
8
- object type
7
9
- nested table and varray
8
10
9
-
Advanced data-comparison options are available for the [`equal`](expectations.md#equal) and [`include / contain`](expectations.md#include--contain) matcher.
11
+
Advanced data-comparison options are available for the [`equal`](expectations.md#equal) and [`contain`](expectations.md#include--contain) matcher.
10
12
11
13
## Syntax
12
14
@@ -164,7 +166,7 @@ Above test will result in two differences of one row extra and one row missing.
164
166
165
167
**Note**
166
168
167
-
> `include / contain` matcher is not considering order of compared data-sets. Using `unordered` makes no difference (it's default)
169
+
> `contain` matcher is not considering order of compared data-sets. Using `unordered` makes no difference (it's default)
168
170
169
171
170
172
## Join By option
@@ -375,10 +377,10 @@ end;
375
377
376
378
## Unordered columns / uc option
377
379
378
-
If you need to perform data comparison of cursors without strictly deending on column order in the returned result-set, use the `unordered_columns` option.
380
+
If you need to perform data comparison of compound data types without strictly depending on column order in the returned result-set, use the `unordered_columns` option.
379
381
Shortcut name `uc` is also available for that option.
380
382
381
-
Expectations that compare cursor data with `unordered_Columns` option, will not fail when columns are ordered differently.
383
+
Expectations that compare compound data type data with `unordered_columns` option, will not fail when columns are ordered differently.
382
384
383
385
This option can be useful whn we have no control over the ordering of the column or the column order is not of importance from testing perspective.
Annotations are used to configure tests and suites in a declarative way similar to modern OOP languages. This way, test configuration is stored along with the test logic inside the test package.
0 commit comments