XUnit/FsUnit测试抛出空引用异常，异常行存疑

问题重现 #

测试用例代码：

module CustomerTests
open Xunit
open FsUnit
open MyProject.Customer
open MyProject.Customer.Domain
    
module ``When upgrading customer`` = 
  let customerVIP = {Id = 1; IsVip = true; Credit = 0.0M}
  let customerSTD = {Id = 2; IsVip = false; Credit = 100.0M}
  [<Fact>]
  let ``should give VIP customer more credit`` () =
    let expected = {customerVIP with Credit = customerVIP.Credit + 100.0M }
    let actual = upgradeCustomer customerVIP
    actual |> should equal expected

运行测试时报错：

[xUnit.net 00:00:00.64] CustomerTests+When upgrading customer.should give VIP cstomer more credit [FAIL]
  Failed CustomerTests+When upgrading customer.should give VIP cstomer more credit [3 ms]
  Error Message:
  System.NullReferenceException : Object reference not set to an instance of an object.
  Stack Trace:
    at CustomerTests.When upgrading customer.should give VIP cstomer more credit() in /Users/user/code/fsharp/CustomerProject/CustomerTests.fs:line 12

堆栈指向记录初始化行，但FSI中执行正常。

排查步骤 #

1. 移除非测试方法级别的绑定 #

F#模块级let绑定会在模块首次加载时执行，XUnit的测试初始化上下文可能和FSI不同，导致模块初始化时的异常被抛到测试方法的堆栈中，造成行号错位。把测试数据移到方法内部：

[<Fact>]
let ``should give VIP customer more credit`` () =
  // 把测试数据移到方法内，避免模块初始化时的潜在问题
  let customerVIP = {Id = 1; IsVip = true; Credit = 0.0M}
  let expected = {customerVIP with Credit = customerVIP.Credit + 100.0M }
  let actual = upgradeCustomer customerVIP
  actual |> should equal expected

重新运行测试，看异常是否消失或行号是否准确。

2. 修复调试信息错位 #

编译优化或未重新编译可能导致堆栈行号不准确：

• 执行dotnet clean清理编译缓存，再dotnet build重新构建测试项目
• 在测试项目的.fsproj文件中添加编译选项关闭优化，确保调试信息准确：

  <PropertyGroup>
    <Optimize>false</Optimize>
  </PropertyGroup>
  

重新运行测试，查看更新后的堆栈跟踪，定位真正的异常位置。

3. 检查upgradeCustomer的隐性依赖 #

FSI环境中可能自动初始化了某些依赖，但测试环境中没有：

• 检查upgradeCustomer函数内部是否依赖静态配置、数据库连接或其他未在测试环境初始化的服务
• 尝试在测试方法中直接调用upgradeCustomer的核心逻辑（剥离外部依赖），验证纯业务逻辑是否正常
• 如果函数依赖依赖注入的服务，确保测试中已正确初始化对应的Mock或测试实例

4. 验证记录类型定义 #

确认MyProject.Customer.Domain中的Customer记录定义正确，没有隐藏的属性或可变状态导致空引用：

// 确保是纯记录类型，无自定义getter/setter
type Customer = {
  Id: int
  IsVip: bool
  Credit: decimal
}

5. 替换断言库排查 #

暂时用XUnit原生断言替换FSUnit的断言，排除断言库本身的问题：

// 替换FSUnit的actual |> should equal expected为：
Assert.Equal(expected, actual)

内容的提问来源于stack exchange，提问作者Knows Not Much