Skip to content

Not all suites are found by suitepath #974

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.

Sign up for GitHub

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

Jump to bottom
Closed
jgebal opened this issue Jul 14, 2019 · 2 comments · Fixed by #978
Closed

Not all suites are found by suitepath #974

jgebal opened this issue Jul 14, 2019 · 2 comments · Fixed by #978
Labels
bug

Comments

@jgebal
Copy link
Member

jgebal commented Jul 14, 2019

Describe the bug
Current implementation of ut_runner.get_suites_info doesn't always return suites.

This is visible when trying to find one of our test suites:

SELECT *
  FROM TABLE(ut_runner.get_suites_info(upper('UT3$USER#'), upper('EXPECTATIONS')));

The query should return data but it isn't

Provide version info
3.1.8-develop
@jgebal jgebal added the bug label Jul 14, 2019
@jgebal
Copy link
Member Author

jgebal commented Jul 14, 2019 •
edited
Loading

This query however provides valid output:

SELECT *
  FROM TABLE(ut_runner.get_suites_info(upper('UT3$USER#')))
  WHERE item_type = 'UT_SUITE'
    and object_name = 'EXPECTATIONS';

This form is however not recommended as it's much slower to process.

@jgebal
Copy link
Member Author

jgebal commented Jul 14, 2019

This was introduced in 3.1.8-develop

jgebal added a commit that referenced this issue Jul 16, 2019
@jgebal
Fixed issue with get_Cached_suite_rows syntax.
11b5f84 
Resolves #974
This was referenced Jul 16, 2019
Closed
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixed issue with get_Cached_suite_rows syntax. utPLSQL/utPLSQL
1 participant
@jgebal