When running rust unit tests it is very useful to utilize the attribute macro #[should_panic(expect = )] to assert that the test is panicking with the correct error message (which means it's panicking at the line you want it to panic and not because of a different error).
However, in applications that use standardized error messages defined in an errors.rs file, it is not possible to pass the constant for the error message as the argument for expect. This:
pub const ERR_001: &str = "ERR_001 message";
#[test]
#[should_panic(expected = ERR_001)]
fn test_function() {
//test code here
}
yields the error:
error: expected unsuffixed literal or identifier, found `ERR_001`
--> staking/src/storage.rs:74:31
|
74 | #[should_panic(expected = ERR_001)]
|
Because the attribute macro only accepts string literals as parameters in expect. Is there a way to work around this limitation? I've research a lot of projects and they all seem to simply rewrite the string instead of referencing the constant, which seems to be a very poor solution.
In case there is no envisioned solution, this should become a feature request, so that tests become easier to maintain in case the strings for error codes change.