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

Skip to content

fix(doc): Update running-unit-tests.md - remove example #1261

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Aug 29, 2023

Conversation

gassenmj
Copy link
Contributor

@gassenmj gassenmj commented Jul 7, 2023

Just stumbled across a duplicate in Your (excellent!!) documentation. I think it can be removed. Thanks for utplsql <3

@jgebal
Copy link
Member

jgebal commented Jul 9, 2023

Hi @gassenmj
It is great to see that someone is actually reading the documentation 😄

There is a slight difference n the two examples. and the documentation does not do a great job describing the differnece.

You can run tests by passing individual items to be executed as elements of the ut_varchar2_list table type.

set serveroutput on
begin
  ut.run(ut_varchar2_list('hr.test_apply_bonus','cust'));
end;

You can run tests by passing all items as a comma-separated-list of values into a single element of the ut_varchar2_list table type.

set serveroutput on
begin
  ut.run(ut_varchar2_list('hr.test_apply_bonus,cust)');
end;

See the difference:

begin
  ut.run(ut_varchar2_list('hr.test_apply_bonus','cust'));
  ut.run(ut_varchar2_list('hr.test_apply_bonus,cust)');
end;

The framework is very flexible in terms of format for this input parameter.

Perhaps better description of those examples would bring more value to the documentation.

What are your thoughts?

@jgebal jgebal merged commit d0cdc63 into utPLSQL:develop Aug 29, 2023
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