@test_throws make it difficult to debug unexpected exceptions

I’m using @test_throws in a unit test to verify that the case being tested throws an expected exception.

When that code throws a dipperent exception the test fails without giving a stack trace. It seems to me that if a different exception is thrown that is a program bug that should be investigated, just like if the exception occurred ouside of the context of @test_throws.

Is there something like @test_throws that behaves in this way, or should I just use try/catch instead of @test_throws? I did a bit of searching but didn['t find one.