I’m trying to test my contract function that uses crypto-primitives. When I try to test it a testcase that does not use the mock (added #[cfg(feature = “crypto-primitives”)]) on top of test function, the test function is not executed when I run cargo concordium test. Thought of skipping cargo concordium test and doing the test via concordium-client invoke with a json param, but unfortunately it is giving an error (rejected because signature verify is not valid) that I don’t know the root cause of, which I think could have been caught by properly executing my unit test. Can you please help how to resolve this bypass error when turning on the feature crypto-primitive?
I’m using a macos