Skip to content

throws works with uninitialized exception variables - #1366

Merged
jgebal merged 6 commits into
developfrom
feature/throws_support_for_uninitialized_exceptions
Jun 9, 2026
Merged

throws works with uninitialized exception variables#1366
jgebal merged 6 commits into
developfrom
feature/throws_support_for_uninitialized_exceptions

Conversation

@jgebal

@jgebal jgebal commented Jun 9, 2026

Copy link
Copy Markdown
Member

It is now possible to reference an uninitialized exception variable name.
utPLSQL will handle the exception properly.

Resolves: #1340

jgebal added 2 commits June 9, 2026 14:37
@jgebal
throws works with uninitialized exception variables
34bedae 
It is now possible to reference an uninitialized exception variable name.
utPLSQL will handle the exception properly.

Resolves: #1340
@jgebal
throws works with uninitialized exception variables
71e7aba 
It is now possible to reference an uninitialized exception variable name.
utPLSQL will handle the exception properly.

Resolves: #1340
@jgebal jgebal self-assigned this Jun 9, 2026
@github-actions

github-actions Bot commented Jun 9, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Test Results

    1 files  ±0    103 suites  ±0   3m 5s ⏱️ -3s
1 131 tests +2  1 127 ✅ +2  4 💤 ±0  0 ❌ ±0 
1 135 runs  +2  1 127 ✅ +2  8 💤 ±0  0 ❌ ±0 

Results for commit 797e401. ± Comparison against base commit c00a746.

This pull request removes 4 and adds 6 tests. Note that renamed tests count towards both. 
utplsql.ut3_tester.core.annotations.test_annot_throws_exception ‑ Gives failure when a exception is expected and nothing is thrown
utplsql.ut3_tester.core.annotations.test_annot_throws_exception ‑ Gives failure when the raised exception is different that the annotated one using variable
utplsql.ut3_tester.core.annotations.test_annot_throws_exception ‑ Success when match exception even if other variable on list dont exists
utplsql.ut3_tester.core.annotations.test_annot_throws_exception ‑ Success when one of exception from mixed list of number and constant is thrown

utplsql.ut3_tester.core.annotations.test_annot_throws_exception ‑ Gives failure when an exception is expected and nothing is thrown
utplsql.ut3_tester.core.annotations.test_annot_throws_exception ‑ Gives failure when the raised exception is different than the annotated one using variable
utplsql.ut3_tester.core.annotations.test_annot_throws_exception ‑ Success when match exception even if another variable on list doesn't exists
utplsql.ut3_tester.core.annotations.test_annot_throws_exception ‑ Success when one of exception from a mixed list of number and constant is thrown
utplsql.ut3_tester.core.annotations.test_annot_throws_exception ‑ Uninitialized exception variable can be used successfully in a test
utplsql.ut3_tester.core.annotations.test_annot_throws_exception ‑ a Failure report shows all expected exceptions

♻️ This comment has been updated with latest results.

@codecov

codecov Bot commented Jun 9, 2026 •
edited
Loading

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.81%. Comparing base (c00a746) to head (797e401).
⚠️ Report is 1 commits behind head on develop.

Additional details and impacted files 
@@             Coverage Diff             @@
##           develop    #1366      +/-   ##
===========================================
- Coverage    94.87%   94.81%   -0.06%     
===========================================
  Files          111      111              
  Lines         5459     5460       +1     
  Branches        30       31       +1     
===========================================
- Hits          5179     5177       -2     
- Misses         263      266       +3     
  Partials        17       17
Flag Coverage Δ
19se 94.80% <100.00%> (-0.06%) ⬇️
21XE 94.95% <100.00%> (-0.06%) ⬇️
23-free 94.57% <100.00%> (-0.08%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@sonarqubecloud

sonarqubecloud Bot commented Jun 9, 2026

Copy link
Copy Markdown

Quality Gate Passed Quality Gate passed

Issues
2 New issues
4 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

@jgebal
jgebal merged commit e47ec38 into develop Jun 9, 2026
14 of 15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@jgebal jgebal

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@jgebal