@@ -7,6 +7,7 @@ Example of unit test procedure body with a single expectation.
77``` sql
88begin
99 ut .expect ( ' the tested value' ).to_equal(' the expected value' );
10+ ut .expect ( ' the tested value' ).to_( equal(' the expected value' ) );
1011end;
1112```
1213
@@ -19,13 +20,12 @@ Pseudo-code:
1920 ut .expect ( a_actual {data- type} ).not_to( {matcher} );
2021```
2122
22- Most of the matchers have shortcuts like:
23+ All matchers have shortcuts like:
2324``` sql
2425 ut .expect ( a_actual {data- type} ).to_{matcher};
2526 ut .expect ( a_actual {data- type} ).not_to{matcher};
2627```
2728
28-
2929# Matchers
3030utPLSQL provides following matchers to perform checks on the expected and actual values.
3131- ` be_between `
183183```
184184The `a_nulls_are_equal` parameter decides on the behavior of `null=null` comparison (**this comparison by default is true!**)
185185
186- There are no shortcuts for `not_to_equal`, so use `not_to (equal(...))`
187-
188186### Comparing cursors
189187
190188The `equal` matcher accepts additional parameter `a_exclude varchar2` or `a_exclude ut_varchar2_list`, when used to compare `cursor` data.
@@ -270,7 +268,7 @@ create or replace package body test_get_events is
270268 ut.reset_nls();
271269
272270 ut.expect(l_actual).to_equal(l_expected);
273- ut.expect(l_actual).not_to( equal( l_expected_bad_date) );
271+ ut.expect(l_actual).not_to_equal( l_expected_bad_date);
274272 end;
275273
276274end;
385383
386384Syntax of check for matcher evaluating to false:
387385` ` ` sql
388- begin
389- ut.expect( a_actual {data-type} ).not_to( {matcher} );
386+ begin
390387 ut.expect( a_actual {data-type} ).not_to_{matcher};
388+ ut.expect( a_actual {data-type} ).not_to( {matcher} );
391389end;
392390` ` `
393391
0 commit comments