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

Skip to content

"Call params for test are not valid" for all tests in specific schema #885

Closed
@tkleiber

Description

@tkleiber

Describe the bug
The error message happens for all tests in a specific schema

Provide version info
utPLSQL v3.1.6.2735, Database version 18.5.0.0.0
port_string: x86_64/Linux 2.4.xx

Information about client software

  • SQL Developer
  • CLI

To Reproduce
Steps to reproduce the behavior:

  1. Create betwnstr/test_betweenstr packages from demo project
  2. EXECUTE ut.run('SCHEMA.test_betwnstr');
  3. See error

Between string function
Returns substring from start position to end position [,003 sec] (FAILED - 1)
Returns substring when start position is zero [,002 sec] (FAILED - 2)
Returns string until end if end position is greater than string length [,002 sec] (FAILED - 3)
Returns null for null input string value [,002 sec] (FAILED - 4)
A demo of test raising runtime exception [,002 sec] (FAILED - 5)
A demo of failing test [,002 sec] (FAILED - 6)
Demo of a disabled test [0 sec] (DISABLED)

Failures:

  1. normal_case
    Call params for test are not valid: package does not exist or is invalid: SCHEMA.TEST_BETWNSTR
  2. zero_start_position
    Call params for test are not valid: package does not exist or is invalid: SCHEMA.TEST_BETWNSTR
  3. big_end_position
    Call params for test are not valid: package does not exist or is invalid: SCHEMA.TEST_BETWNSTR
  4. null_string
    Call params for test are not valid: package does not exist or is invalid: SCHEMA.TEST_BETWNSTR
  5. bad_params
    Call params for test are not valid: package does not exist or is invalid: SCHEMA.TEST_BETWNSTR
  6. bad_test
    Call params for test are not valid: package does not exist or is invalid: SCHEMA.TEST_BETWNSTR
    Finished in ,014138 seconds
    7 tests, 0 failed, 6 errored, 1 disabled, 0 warning(s)

Expected behavior
Should be successfully run as in another schema in the same database.

Example code
betwnstr/test_betweenstr packages from demo project

Additional context
Maybe this is grant / object related (eg. duplicate system views in the schema or similar)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions