GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Cannot navigate to failed test with throws annotation · Issue #89 · utPLSQL/utPLSQL-SQLDeveloper

Cannot navigate to failed test with throws annotation #89

New issue
Copy link
New issue
Copy link
Closed
#90
Closed
Cannot navigate to failed test with throws annotation#89
#90
Copy link
Assignees
PhilippSalvisberg
Labels
bug
Milestone
v1.1.1

Description

@PhilippSalvisberg
PhilippSalvisberg
opened on Dec 15, 2019
Issue body actions

@tkleiber mentioned this issue at the DOAG conference and sent detailed information via Twitter. I could reproduce it. Here's a simplified version.

1. Create the following package specifications without bodies

CREATE OR REPLACE PACKAGE pkg1 IS
   --%suite
   
   --%throws(-20501)
   --%test
   PROCEDURE p;
END;
/

CREATE OR REPLACE PACKAGE pkg2 IS
   --%suite
   
   --%test
   PROCEDURE p;
END;
/

2. Run them in a SQL Developer worksheet

SET SERVEROUTPUT ON SIZE UNLIMITED
EXECUTE ut.run;

and the result looks good:

pkg1
  p [.11 sec] (FAILED - 1)
 
pkg2
  p [.094 sec] (FAILED - 2)
 
Failures:
 
  1) p
      Actual: -4067 was expected to equal: -20501
      ORA-04067: not executed, package body "SCOTT.PKG1" does not exist
      ORA-06508: PL/SQL: could not find program unit being called: "SCOTT.PKG1"
      ORA-06512: at line 6
       
  2) p
      ORA-04067: not executed, package body "SCOTT.PKG2" does not exist
      ORA-06508: PL/SQL: could not find program unit being called: "SCOTT.PKG2"
      ORA-06512: at line 6
Finished in .211323 seconds
2 tests, 1 failed, 1 errored, 0 disabled, 0 warning(s)

3. Run the same tests with the realtime reporter in SQL Developer

image
This looks good. You can click on the second test and click on every single tab (test, failures, errors, warnings, info). But when you click on the first test the GUI is blocked. You cannot navigate successfully to the first test. The following screenshot shows the inconsistencies.
image

4. Workaround (not really)

Create a package body for the test with the throws annotation, like this:

CREATE OR REPLACE PACKAGE BODY pkg1 IS
   PROCEDURE p IS
   BEGIN
      raise_application_error(-20501, 'some error');
   END;   
END;
/

When the test succeeds then the GUI behaves as expected. When the test fails, then navigation to the failed test is not possible.

Activity

  1. PhilippSalvisberg
    added
    bug
    on Dec 15, 2019
  2. PhilippSalvisberg
    self-assigned this
    on Dec 15, 2019
  3. PhilippSalvisberg commented on Dec 15, 2019

    @PhilippSalvisberg
    PhilippSalvisberg
    on Dec 15, 2019
    MemberAuthor
    More actions

    It's a NPE. caller in Expectation is null...

  4. PhilippSalvisberg
    closed this as completedin #90on Dec 15, 2019
  5. PhilippSalvisberg
    added this to the v1.2.0 milestone on Dec 15, 2019
  6. PhilippSalvisberg
    modified the milestones: v1.2.0, v1.1.1 on May 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

  • @PhilippSalvisberg
    PhilippSalvisberg

Labels

bug

Type

No type

Projects

No projects

    Milestone

    • v1.1.1

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    You are visitor 01402503 — GeezerVison does not store the pages you look up.
    Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.