Bad custom test names should not fail silently about test-case HOT 4 OPEN

That's an exciting idea. However, the intention was to provide a human-readable test description, not necessarily a compiler-readable one. For example:

    #[test_case(4,  2  ; "when operands are swapped")]
    #[test_case(-2, -4 ; "when both operands are negative")]
    #[test_case(2,  4  ; "when both operands are positive")]

As you can see, in this example, we have to sanitize input.

Anyway, you have a valid point. @luke-biel - perhaps we should introduce some kind of feature flag or syntax (like different quotes used) to enable "strict mode"?

from test-case.

the intention was to provide a human-readable test description, not necessarily a compiler-readable one.

Hmm, yes, that makes sense

from test-case.

perhaps we should introduce some kind of feature flag or syntax (like different quotes used) to enable "strict mode"?
@frondeus I'd see extra arg to test case rather than changing syntax of the description.

#[test_case(4, 2 ; "when operands are swapped", fn_name = my_very_custom_name)]

I'm just not sure if this doesn't introduce bloat within test-case - how many people are gonna use it?

from test-case.

IMHO, a project using test_case should almost always add a name to the test, for good practices. But I think refining the opposite is still something good.

The solution provided on #19 would solve this problem, but the question is: what defined a "bad test name"? Anything besides alphanumeric, spaces, and underscores?

from test-case.