Uh oh!
There was an error while loading. Please reload this page.
Simplify TestIsActivationJobNeeded to match unconditional source behavior - #53447
Merged
pelikhan merged 2 commits intoAug 17, 2026
Merged
Conversation
6 tasks
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
CopilotAI
changed the title
[WIP] Improve test quality in is_task_job_needed_test.goSimplify TestIsActivationJobNeeded to match unconditional source behaviorAug 17, 2026
pelikhan
marked this pull request as ready for review
August 17, 2026 18:50
Contributor
There was a problem hiding this comment.
Pull request overview
Simplifies activation-job testing to reflect its unconditional behavior.
Changes:
- Replaces four redundant subtests with one
assert.True. - Removes misleading unused
WorkflowDatasetup. - Documents why the activation job is always required.
Show a summary per file
| File | Description |
|---|---|
pkg/workflow/is_task_job_needed_test.go | Streamlines and clarifies the activation-job test. |
Review details
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Balanced
Contributor
🎉 This pull request is included in a new release. Release: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
isActivationJobNeeded()takes no parameters and unconditionally returnstrue(compiler_jobs.go:23-31), but its test had four subtests that each constructed aWorkflowData, discarded it viavar _ = datainside an immediately-invoked closure, and asserted the same constant. The subtests were functionally identical and implied a dependency onWorkflowDatathat does not exist.Changes
WorkflowDataconstruction andvar _ = dataclosures.if !cond { t.Errorf(...) }toassert.True, consistent withcompiler_jobs_test.goin the same package.Before:
After:
referencesCustomJobOutputsandjobDependsOnPreActivationwere left alone — already covered incompiler_jobs_test.goandcustom_job_condition_test.go, with no duplication drift observed.