> **Rubberduck version information**

```
Version 2.5.2.5906
OS: Microsoft Windows NT 10.0.19042.0, x64
Host Product: Microsoft Office x64
Host Version: 16.0.13929.20296
Host Executable: EXCEL.EXE
```

**Description**
Somewhen a bug was introduced that testing with the `PermissiveAssertClass` a result of `Null` results in a failed test.

**To Reproduce**
```VBA
Option Explicit
Option Private Module

'@TestModule
'@Folder("Tests")

#Const LateBind = LateBindTests

#If LateB

> I tested with 2.5.1 and that had failed the test, too.

However, since the permissive assert is meant to replicate the same result we'd have gotten with VBA, it could be argued that it's correct.

```
?Null = Null
Null
?IIf(Null = Null, True, False)
False
```

So in a sense, it's correct that comparison of 2 `Null` will always be unequal and thus logically false.

Note that we did update the `PermissiveAssert` class sometime ago (I want to say 2.5.0 but would need to verify) and

> > Could you give a hint how LateBindTests works. How can I change the value to select EarlyBind and LateBind? Simply trying to change it to EarlyBindTests doesn't seem to work.

You have two options.

You could change this:
```
#Const LateBind = LateBindTests
```
to:
```
#Const LateBind = 0 ' or 1 if you want late-bound
```

However, this effects only one module, and if you have several test modules, that is not a great idea.

The 2nd option is to define the non-existent condit

> I was looking at the HTTP logs for the website, and between browser sessions and bots every request that came from Rubberduck's VersionCheck comes in with an "unknown" user-agent:


(IP addresses wiped)

Not a high priority at all, but the VersionCheck feature including a "Rubberduck-{version}" user-agent header would be nice.

> I understand you point, So then I'll change my tests to

```vba
'@TestMethod("PermissiveAssertTest")
Private Sub Null_PermissiveAssertTest()
On Error GoTo TestFail

Dim IsResultNull As Boolean
IsResultNull = IsNull(Null)
PermissiveAssert.IsTrue IsResultNull

TestExit:
Exit Sub
TestFail:
PermissiveAssert.Fail "Test raised an error: #" & Err.Number & " - " & Err.Description
Resume TestExit
End Sub
```

Would that be fine or is there a better way

> I understand your point, So then I'll change my tests to

```vba
'@TestMethod("PermissiveAssertTest")
Private Sub Null_PermissiveAssertTest()
On Error GoTo TestFail

Dim IsResultNull As Boolean
IsResultNull = IsNull(Null)
PermissiveAssert.IsTrue IsResultNull

TestExit:
Exit Sub
TestFail:
PermissiveAssert.Fail "Test raised an error: #" & Err.Number & " - " & Err.Description
Resume TestExit
End Sub
```

Would that be fine or is there a better wa