> Perhaps this is an opportunity to revise the ToDO explorer.

Adding 'Description" to the todo explorer will pull up all lines containing the term 'Description'

e.g.
'@Description()
'@Description("")
'@Discription("Wibble wibble")

but also unfortunately

Err.Description

The todo explorer will not detect the terms
@Description
Description()
Description("")


So it would seem to me there are possibly three useful enhancements that could be introduced to the todo explorer.

> `the passing tests indicate that it's basically issuing results for exactly the opposite of when it should be doing that`

Huh? Are you sure? 😮
Here's an example test case:

```
[Test]
[Category("Inspections")]
public void SheetAccessedUsingString_ReturnsResult_AccessingUsingApplicationModule()
{
const string inputCode =
@"Public Sub Foo()
Application.Worksheets(""Sheet1"").Range(""A1"") = ""Foo""
Application.Sheets(""Sheet1"").Range(""A1"") = ""Foo""
End Sub";

> > the passing tests indicate that it's basically issuing results for exactly the opposite of when it should be doing that

Huh? Are you sure? 😮
Here's an example test case:

```
[Test]
[Category("Inspections")]
public void SheetAccessedUsingString_ReturnsResult_AccessingUsingApplicationModule()
{
const string inputCode =
@"Public Sub Foo()
Application.Worksheets(""Sheet1"").Range(""A1"") = ""Foo""
Application.Sheets(""Sheet1"").Range(""A1"") = ""Foo""
End Sub";

> This test case seems to test the wrong thing, indeed.

`Application.Worksheets` basically resolves to `Application.ActiveWorkbook.Worksheets`, which is not the same as `ThisWorkbook.Worksheets`, in general. Using the the code name yields the same result as the latter. The active workbook might be an entirely different workbook to which there is no reference on compile time.