Code inspection errors

[Michael Huffaker]

Hi Scott,

Found two more code inspection errors on the code that existed before 2.0 so I wanted to send you a picture of the errors so you can get to them when you can.

[Scott Wells]

Thanks, Michael! Can you tell me about TestUtils in these two screenshots? Is it a top-level class or an inner class? Is it annotated in any particular way, e.g., @TestVisible? Are there multiple types with that name in your project? Info like that will help me to reproduce the issue.

[Scott Wells]

Hi, Michael. Just wanted to follow up and see if you could provide a little more info about the code underlying these false negatives. The issue appears to be starting with the inability to resolve TestUtils, so I was wondering where that class is defined, its visibility, and anything else that might prevent IC from being able to resolve it from that particular point in your code. Thanks!

[Michael Huffaker]

Hi Scott, Sorry about the delay in my reply - its been a crazy week. The TestUtils class being referenced in this code is a top level class ( public class TestUtils {} ) and it turns out that there are two other TestUtils classes in our system - both have their own namespace and are controlled with a managed package.

[Scott Wells]

No problem at all, Michael. You're helping me! Okay, so there are three classes called TestUtils, one in the local project and two from other namespaces. Sounds like it's getting confused about which to use. Should give me what I need to reproduce and fix it. Thanks!

[Michael Huffaker]

You're welcome :) If you need anything else let me know.

[Scott Wells]

Reproduced successfully and fixed for the next build. Thanks!

[Scott Wells]

Delivered in 2.0.0.3. Let me know if you find any new ones.