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 — Support for data driven testing · Issue #1265 · utPLSQL/utPLSQL

Support for data driven testing  #1265

New issue
Copy link
New issue
Copy link
Closed as duplicate
Closed as duplicate
Support for data driven testing #1265
Copy link

Description

@UdiPlsql
UdiPlsql
opened on Aug 5, 2023
Issue body actions

Is your feature request related to a problem? Please describe.
It would be better that we have an option for data driven testing using a data table similar to junit. The purpose is, then we could iterate the same invocation for method under test for multiple data input combinations.

Example

Inputparam1|Inputparam2|expected
10|uditha|success
0|guest|unsuccess

So that we could iterate the test for multiple input combinations.

Data driven approach for unit testing is more powerful. Because a developer could improve the test coverage by expanding the data table.

Note

Please do not create issues for generic SQL or PL/SQL questions. There are other forums and communities to help you with those. See ASKTom for example.

Want to discuss
If you want to discuss your issue, join our SLACK chat.

Activity

  1. lwasylow commented on Aug 5, 2023

    @lwasylow
    lwasylow
    on Aug 5, 2023
    Member
    More actions

    This is duplicate #1028
    As for data driven current approach is debatable but more likely I would be inclined to implement parameters and let users create own data tables if needs be.
    However parameters are quite complex subject given you should be able pass any type and any number.

    Have you considered implementation of a loop in your own test for example
    For I in select from data table
    Loop
    Execute proc with param
    Assert, result
    End loop

    It will not produce a multiple test results in report but will achieve task.

    Cheers Lukasz

  2. UdiPlsql commented on Aug 5, 2023

    @UdiPlsql
    UdiPlsql
    on Aug 5, 2023
    Author
    More actions

    Thanks Lukasz,

    Yes.. you are right about parameters. It is a complex matter with different types as well as with parameter list varies from function to function.

    Yes we intend to use 'loop' for data driven tests, but we are more excited to see an option similar to Junit OR testNG style param tables should possible.

  3. jgebal commented on May 9, 2026

    @jgebal
    jgebal
    on May 9, 2026
    Member
    More actions

    The discussion is moved to #1326

  4. jgebal
    closed this as a duplicateof Parameter drive tests #151 on May 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      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.