Skip to content

fix: improve no tests in org error message, suggest actions W-17866064 #706

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 3 commits into from
Mar 18, 2025
Merged

fix: improve no tests in org error message, suggest actions W-17866064 #706

merged 3 commits into from
Mar 18, 2025

Conversation

WillieRuemmele
Copy link
Contributor

@WillieRuemmele WillieRuemmele commented Mar 17, 2025 •
edited
Loading

What does this PR do?

improves error message when no tests in the org from
Error (1): Always provide a classes, suites, tests, or testLevel property.

to

Error (INVALID_INPUT): There are no apex tests to run in the org

Try this:

Ensure Apex Tests exist in the org

What issues does this PR fix or reference?

@W-17866064@
forcedotcom/cli#3217

cristiand391
cristiand391 reviewed Mar 18, 2025
View reviewed changes
cristiand391
cristiand391 requested changes Mar 18, 2025
View reviewed changes
Copy link
Member

@cristiand391 cristiand391 left a comment

Choose a reason for hiding this comment

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

just one small request around error handling.

@cristiand391
Copy link
Member

QA notes:

✅ see new error running apex run test against org with no tests
✅ other errors are ignored:
Screenshot 2025-03-18 at 16 33 21

@cristiand391 cristiand391 merged commit e14ab5b into main Mar 18, 2025
15 checks passed
@cristiand391 cristiand391 deleted the wr/improveError branch March 18, 2025 19:34
@zenibako zenibako mentioned this pull request Mar 27, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@cristiand391 cristiand391 cristiand391 approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@WillieRuemmele @cristiand391