"Always provide a classes, suites, tests, or testLevel property." when running `sfdx force:apex:test:run -l RunLocalTests` on a project with no tests about salesforcedx-apex HOT 7 OPEN

@randi274 Well in this case I thought the org had tests but it didn't. But the error message tells me I did something wrong on the command line (I didn't specify a test level, test suite, or list of tests) when in fact the "error", if you want to call it that, was that there were no (local) tests on the org. A good error message not only tells the user what's wrong, but also gives some indication as to how to fix it.

So I think it just avoids confusion when you tell the user what the actual problem is instead of confusing them by saying they need to specify a test level when they did specify a test level.

If I say rm bla on the command line, I get an error that says rm: bla: No such file or directory. It doesn't say rm: You have to specify a file to unlink. So I think it's reasonable to expect the same from the Salesforce CLI.

Hope this helps!

from salesforcedx-apex.

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

from salesforcedx-apex.

please uninstall the salesforcedx plugin and try again. That makes a bunch of your CLI commands, including apex, out of date by months.

sfdx plugins:uninstall salesforcedx

from salesforcedx-apex.

OK, tried that but the result is the same.

However, I think the problem might be that the org I'm testing against has no local tests. So it might be a case of needing a clearer error message -- or just accepting the fact that in an org with no tests, running all local tests means running no tests, which is absolutely fine: if I ask you to give me all your Ferraris and you give me zero, that's probably because you don't have any Ferraris ;-)

I'll update the issue title and description.

from salesforcedx-apex.

I'm transferring to the repo that tracks issues for all apex:* commands

from salesforcedx-apex.

@fransf-wtax I was able to reproduce the error message, but can you provide us a little more detail as to why you would be running this command in an org without tests? (If I omit the -l parameter, I still encounter the issue!). That will help us figure out prioritizing this issue. I also am not finding this error in any of our extension or libraries, so I think this might be something that we're getting back upstream from Salesforce proper.

from salesforcedx-apex.

Thanks for the additional information @fransf-wtax! @smaddox-sf this would be a product question on how we should handle it - this is an error message that we get back from core, so we could provide a check for orgs without tests, handle the error message more politely, or leave it as-is as a somewhat confusing message.

from salesforcedx-apex.