Add unit test for invalid workflow entry name error handling#6409
Merged
pditommaso merged 3 commits intomasterfrom Sep 21, 2025
Merged
Add unit test for invalid workflow entry name error handling#6409pditommaso merged 3 commits intomasterfrom
pditommaso merged 3 commits intomasterfrom
Conversation
This commit adds a comprehensive unit test to validate the fix for PR #6404 that prevents "Strings must not be null" errors when an invalid workflow entry name is specified. The test verifies that: - Using an invalid entry name (e.g., `nextflow run script.nf -entry invalidEntry`) - Correctly throws IllegalArgumentException with proper error message - Shows "Unknown workflow entry name: invalidEntry" instead of "Strings must not be null" - Includes suggestions for valid workflow names when available The test also includes a fix to ensure null workflow names are filtered out of the imports section in getWorkflowNames(), making the fix comprehensive for both local definitions and imports. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
✅ Deploy Preview for nextflow-docs-staging canceled.
|
bentsherman
reviewed
Sep 16, 2025
modules/nextflow/src/main/groovy/nextflow/script/ScriptMeta.groovy
Outdated
Show resolved
Hide resolved
bentsherman
reviewed
Sep 16, 2025
modules/nextflow/src/test/groovy/nextflow/script/ScriptDslTest.groovy
Outdated
Show resolved
Hide resolved
….groovy [ci fast] Co-authored-by: Ben Sherman <bentshermann@gmail.com> Signed-off-by: Paolo Di Tommaso <paolo.ditommaso@gmail.com>
…oovy [ci skip] Co-authored-by: Ben Sherman <bentshermann@gmail.com> Signed-off-by: Paolo Di Tommaso <paolo.ditommaso@gmail.com>
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 free
to 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.
Summary
This PR adds a comprehensive unit test to validate the fix implemented in PR #6404 that prevents "Strings must not be null" errors when an invalid workflow entry name is specified via the
-entryparameter.Related Issues:
Background
The original issue (#6405) occurred when running:
Instead of showing a helpful error message like "Unknown workflow entry name: invalidEntryName", users would see a confusing "Strings must not be null" error. This was fixed in PR #6404, and this PR adds comprehensive tests to prevent regression.
Changes Made
🧪 New Unit Test (
ScriptDslTest.groovy)should show proper error message for invalid entry nametestIllegalArgumentExceptionwith proper error message🔧 Enhanced Fix (
ScriptMeta.groovy)getWorkflowNames()&& item.namecheck for imported workflows (matching the existing fix for local definitions)Test Validation
The test has been validated by:
Test Details
Impact
This test will catch any future regressions and ensures users always receive clear, actionable error messages when specifying invalid workflow entry names.
🤖 Generated with Claude Code