Enhancement: Allow for orchestrator validation job to skip certain classes about sfpowerscripts

[nawforce]

Don't think this has come up before. There are a few cases you would need to think about re: 'no code', such as would that include having code in superclasses, what about property blocks, field initialisers and initialiser blocks. But mostly its just deciding what the rules are and writing some code to inspect the class after parsing to see if it fits that. There might also be some odd cases to deal with, such as a method that does nothing.

[azlam-abdulsalam]

@Stian-Schikora this is a good idea, Can we write a DR on this? Probably it would be better if we could do this without any comments at all, by doing an apex parse run on it.

@nawforce have you looked into similar scenarios?

[azlam-abdulsalam]

Thanks @nawforce. Will start with the comment as @Stian-Schikora suggested and then look into what are the rules

[ruslan-kurchenko]

We went via a straightforward and dummy approach. In such a case, we create a private test visible method, which is empty, and a test method called coverage() calls such methods to satisfy the requirement.

[azlam-abdulsalam]

@ruslan-kurchenko @Stian-Schikora further thoughts? close this one?