Identify error source in stacktrace for bad params in function call.

[grapevinegizmos]

In my unit tests, I get errors like this, which I have come to recognize as a some kind of invalid parameter in a smart contract function call:

1) makeNFT
       "before each" hook for "should transfer ownership":
     Error: invalid address or ENS name (argument="name", value=undefined, code=INVALID_ARGUMENT, version=contracts/5.7.0)
      at Logger.makeError (node_modules/@ethersproject/logger/src.ts/index.ts:269:28)
      at Logger.throwError (node_modules/@ethersproject/logger/src.ts/index.ts:281:20)
      at Logger.throwArgumentError (node_modules/@ethersproject/logger/src.ts/index.ts:285:21)
      at /Users/joshkramer/Documents/VSCodeProjects/BKopy/bkopy-nft-contracts/node_modules/@ethersproject/contracts/src.ts/index.ts:123:16
      at step (node_modules/@ethersproject/contracts/lib/index.js:48:23)
      at Object.next (node_modules/@ethersproject/contracts/lib/index.js:29:53)
      at fulfilled (node_modules/@ethersproject/contracts/lib/index.js:20:58)
      at processTicksAndRejections (node:internal/process/task_queues:96:5)
      at runNextTicks (node:internal/process/task_queues:65:3)
      at listOnTimeout (node:internal/timers:528:9)

While the stack trace is useful in that it at least identifies which function of my test is faling, the line number which produced the error is not identified. Sometimes my 'before' setup code is pretty long, and to find the line that's causing the error I have insert several contract.log statemetns to determine which call is causing the error. Would it be possible simply to include the trace the line number of the test method (or if that's not possible, the name of the contract function called) that provoked the error?