Code coverage confused by same class & trigger name

[Davin Casey]

When an apex class & an apex trigger have the same name, code coverage does not accurately report the coverage on the apex class.

See this image:

I have an apex trigger named OutboundPayloadJob and an apex class with the same name. After running all tests, IC is showing 1 of 1 lines covered for the apex class when this is in fact the coverage stats for the trigger. OutboundPayloadJob.class has over 200 lines of code.

[Davin Casey]

For comparison, the developer console correctly shows the coverage for both:

‌

[Scott Wells]

Ah, interesting. Should be a very simple fix. I'll take a look for one of the near-term builds. Thanks for reporting!

[Scott Wells]

I looked at this today and am going to push it out another week or two. It's not as simple a change as expected because right now there are a few places where IC2 currently expects Apex class and trigger names to be unique as a combined set. That's obviously not a valid expectation, but I want to make sure the fix gets the appropriate time and attention.

[Scott Wells]

Fix committed for the next build.

[Scott Wells]

Delivered in 2.1.7.5.