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

Test refactor: separate Task validation tests for propagation #6677

Merged
merged 1 commit into from
May 18, 2023

Conversation

lbernick
Copy link
Member

To support propagated parameters in inline Task specs, validation of variable usage is skipped for inline Task specs and performed only for referenced Tasks. This commit refactors TestTaskSpecValidateError to split out the test cases which rely on this validation logic from test cases that rely on validation logic that is always performed. Since validation logic for usage of declared variables should always be performed when a Task is created directly (but not always for a Task spec), it updates these tests to validate a Task rather than a Task spec. This refactoring will make cleanup for propagated parameters easier. No functional changes.

/kind cleanup
Partially addresses #6647

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • n/a Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
  • Has Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • n/a Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
  • n/a Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

To support propagated parameters in inline Task specs, validation of variable usage
is skipped for inline Task specs and performed only for referenced Tasks.
This commit refactors TestTaskSpecValidateError to split out the test cases which rely
on this validation logic from test cases that rely on validation logic that is always performed.
Since validation logic for usage of declared variables should always be performed when a Task
is created directly (but not always for a Task spec), it updates these tests to validate a Task
rather than a Task spec. This refactoring will make cleanup for propagated parameters easier.
No functional changes.
@tekton-robot tekton-robot added release-note-none Denotes a PR that doesnt merit a release note. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels May 17, 2023
@chitrangpatel
Copy link
Contributor

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label May 17, 2023
@lbernick
Copy link
Member Author

/retest

@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chitrangpatel, dibyom

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 18, 2023
@lbernick lbernick closed this May 18, 2023
@lbernick lbernick reopened this May 18, 2023
@tekton-robot tekton-robot merged commit 4abfe18 into tektoncd:main May 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants