The most robust observability solution for Salesforce experts. Built 100% natively on the platform, and designed to work seamlessly with Apex, Lightning Components, Flow, Process Builder & integrations.
Originally posted by **gauravchaube21** February 1, 2024
We have installed Nebula Logger as an unlocked package in our org. Our pipeline installs the Nebula Logger to a scratch org whenever it gets created. Along with the package, we install the regular metadata and run test classes. This happens via our CI/CD Pipeline. We use the following coming to run the test classes
sf apex run test --test-level RunLocalTests --wait 30 --code-coverage --detailed-coverage --result-format human
Unfortunately, even though we have specified `RunLocalTests` in our sf command, all of the test classes run when running the command. Infact, a lot of test classes fail (Error Message: `Search Unavailable`) when this happens.
It would be great if someone could help us with the reason why the package test classes run even though we explicitly run local test classes and a possible workaround in this situation. Our pipelines are blocked because of the failing test classes within the package.
Thanks in advance
jongpie
commented
9 months ago
Discussed in https://github.com/jongpie/NebulaLogger/discussions/621