Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes #16632: Add testCases property to a test suite source config #16631

Merged
merged 4 commits into from
Jun 19, 2024

Conversation

sushi30
Copy link
Contributor

@sushi30 sushi30 commented Jun 12, 2024

Describe your changes:

enable specifying a subset of test cases to run in a test suite pipeline.

no schema migration is required since the default is null.

Fixes #16632

adds the testCases property to testSuitePipeline.json to enable filtering a subset of test cases to run.

Type of change:

  • Improvement

Checklist:

  • I have read the CONTRIBUTING document.
  • My PR title is Fixes <issue-number>: <short explanation>
  • I have commented on my code, particularly in hard-to-understand areas.
  • For JSON Schema changes: I updated the migration scripts or explained why it is not needed.
  • I have added tests around the new logic.
  • For connector/ingestion changes: I updated the documentation.

enable specifying a subset of test cases to run in a test suite pipeline
@sushi30 sushi30 requested a review from a team as a code owner June 12, 2024 13:12
@github-actions github-actions bot added documentation Improvements or additions to documentation Ingestion backend safe to test Add this label to run secure Github workflows on PRs labels Jun 12, 2024
@sushi30 sushi30 marked this pull request as draft June 12, 2024 13:16
@sushi30 sushi30 changed the title feat: test-suites Fixes #16632: Add testCases property to a test suite source config Jun 12, 2024
@sushi30 sushi30 marked this pull request as ready for review June 12, 2024 14:14
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need to add an isDefault flag to this schema as well. So we can identify the default ingestion pipeline?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

null value resolves the default behavior. its documented in the description. I'd rather avoid adding this field is it has the potential for ambiguity such as:

isDefault: true
testCases: ["what_will_this_do"]

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good. The behavior will be we can have multiple "default" pipelines right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes. this is the same as current behavior. and as we are doing now we can enforce things on the UI side.

Copy link

sonarcloud bot commented Jun 13, 2024

@sushi30 sushi30 merged commit c79c5da into main Jun 19, 2024
32 checks passed
@sushi30 sushi30 deleted the test-case-list branch June 19, 2024 10:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend documentation Improvements or additions to documentation Ingestion safe to test Add this label to run secure Github workflows on PRs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support test case filtering in test suite pipeline
3 participants