You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When running sfp apextests:trigger -u <org> -l RunAllTestsInPackage -c -n <dir> against a namespaced org, the cli fails to detect coverage as generated because
if (!testToBeTriggered.includes(test.apexClass.fullName)) {
testClassesThatDonotContributedCoverage.push(test.apexClass.fullName);
if (!testToBeTriggered.includes(test.apexClass.fullName))
testToBeTriggered.push(test.apexClass.fullName);
}
is comparing the namespaced name against testToBeTriggered which is without namespace.
To Reproduce
Steps to reproduce the behavior:
Create test class in namespace org
Use SFP to run tests with coverage
Observe errors reported to stdout;
Tests to be executed: Foo
later;
Test Classes that were not able to contribute coverage: NAMESPACE.Foo
Expected behaviour
Should properly detect comparison with or without namespace - at risk of colliding coverage results if an unnamespaced class has the same name
Creating this issue with intention of submitting a PR shortly
The text was updated successfully, but these errors were encountered:
Describe the bug
When running
sfp apextests:trigger -u <org> -l RunAllTestsInPackage -c -n <dir>
against a namespaced org, the cli fails to detect coverage as generated becauseis comparing the namespaced name against testToBeTriggered which is without namespace.
To Reproduce
Steps to reproduce the behavior:
later;
Expected behaviour
Should properly detect comparison with or without namespace - at risk of colliding coverage results if an unnamespaced class has the same name
Creating this issue with intention of submitting a PR shortly
The text was updated successfully, but these errors were encountered: