Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Updated documentation.#164

Merged
Pazus merged 3 commits intoutPLSQL:developfrom
jgebal:feature/update_readme
Jan 18, 2017
Merged

Updated documentation.#164
Pazus merged 3 commits intoutPLSQL:developfrom
jgebal:feature/update_readme

Conversation

@jgebal
Copy link
Copy Markdown
Member

@jgebal jgebal commented Jan 17, 2017

No description provided.

Copy link
Copy Markdown
Member

@Pazus Pazus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The doc looks better and better. great!

It's best to give an example to get an idea what is what
```sql
begin
ut.expect( 'the tested value' ).to_( equal('the expected value') );
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why we use to_( equal syntax in examples and not to_equal?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I though to_equal is the primary syntax to use and to_( equal is a more general form

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The to_() is a base syntax for extensible matchers and the to_equal() is just a wrapper.
Not all matcher have wrappers for them and getting developers familiar with the to_ syntax seemed like a good idea.

Comment thread docs/userguide/expectations.md Outdated
ut.expect( a_actual ).to_( match( a_pattern in varchar2, a_modifiers in varchar2 := null) )
```

Parameters `a_pattern` and `a_modifiers` represent a valid regexp pattern accepted by [Oracle regexp_like function](https://docs.oracle.com/cd/E11882_01/server.112/e41084/conditions007.htm#SQLRF00501)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Pazus Pazus added this to the version3 milestone Jan 17, 2017
@rlove rlove changed the base branch from version3 to develop January 17, 2017 21:06
@Pazus Pazus merged commit 1b5ea60 into utPLSQL:develop Jan 18, 2017
@Pazus Pazus removed the in progress label Jan 18, 2017
@jgebal jgebal deleted the feature/update_readme branch January 20, 2017 09:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants