Can not add ingestion pipeline for Testsuite

[hoangdh5]

Slack conversation here: https://openmetadata.slack.com/archives/C02B6955S4S/p1689933249988789

Affected module

• Ingestion Framework

Describe the bug For a table which does not have any test case, go to pipeline then Add Ingestion then click, OM will move to 404 page. For a table which has at least one test case, go to pipeline >>Add Ingestion button not appear. I can not create any Pipeline for any Testsuite.

For Testsuite default for each table, It's not shown on the Data Quality page (test suite tag) so we can not adjust (add or remote) testcase belonging to Testsuite default. If you have some testcase not ready for run, the only way is to delete it then it will not run with other testcase in Testsuite default.

To Reproduce Screenshots or steps to reproduce

Expected behavior

• User can select testsuite and add pipeline in Data Quality
• User can add/remote Testcase in Testsuite default and TestSuite Default should be appear in Dataa Quality Page
• Testcase maybe need a flag (Activate/DeActivate) so when Run Test Suite only Active Testcase is run in stead of delete Testcase or remove from Test Suite.

Version:

• OS: [e.g. iOS]
• Python version:
• OpenMetadata version: OM 1.1
• OpenMetadata Ingestion package version: [e.g. openmetadata-ingestion[docker]==XYZ]

Additional context Add any other context about the problem here.

[ShaileshParmar11]

Hello @hoangdh5 you can only create one pipeline per testSuite

[hoangdh5]

Hi @ShaileshParmar11, how about this expect behavior: "User can select testsuite and add pipeline in Data Quality User can add/remote Testcase in Testsuite default and TestSuite Default should be appear in Dataa Quality Page Testcase maybe need a flag (Activate/DeActivate) so when Run Test Suite only Active Testcase is run in stead of delete Testcase or remove from Test Suite"

12575 as I understand only fix issues related to redirect 404.

About your comment: I agreed that only one pipeline per TestSuite, But I think will be more flexible if we can set pipeline for Custom Testsuite.

[ShaileshParmar11]

ok, the issue got closed by mistake, we need to think about other points, and yes the current solution in #12575 is related to redirection. @hoangdh5

[harshach]

@hoangdh5 CustomTestsuites are more like dashboarding. If a test is created, it will execute in the context of Table's test suite itself. You can create a custom test suite to pick and choose testcase across multiple tables and create a dashboard. If the testcase is already running as part of another table's test suite why do you want to re-run them and add another pipeline to CustomTestsuite

[hoangdh5]

@harshach In operation, some case need to execute testcase not in scheduled, like have to check urgent issues or adhoc request from bussiness unit, or sometime I just want to run a newly testcase added, I have to run all other . Or other usecase like you have some different kind of testcase, and these have to run in different schedule ?. That would be bad if i have to deleted some testcase just because I don't need run it adhoc. I see we have only one testsuite for each table and so only one schedule for all of testcase. I think we can use testsuite for more features not only for group of result/ dashboarding.

[TeddyCr]

Thank you @hoangdh5 for you suggestion. We value your feedback and the contribution you make to enhance the product. We'll be closing this issue as won't fix.

OpenMetadata used to allow execution of logical testSuite where test could be group logically from different tables and executed. Based on the feedback we gather we found it was not the most optimal approach as it created opportunities to duplicate tests and also required users to think about the table refresh schedule to set up the test case. We believe executing all the test cases linked to a table is the best practice to ensure consistent data quality.

Thank you for all your contributions and feedback