You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have a test module called Foo you can't use Foo as the string argument to describe. And, if you do, you get a misleading error message: "The test 'Foo' contains a child test of the same name. Let's rename them so we know which is which"
Sample code:
module Foo exposing (..)
import Expect exposing (Expectation)
import Test exposing (..)
suite : Test
suite =
describe "Foo"
[ test "t1" (\_ -> 1 + 1 |> Expect.equal 2)
]
The "bug" here is that the error message is really bad.
I think I am happy that this combination of module name and describe label is not allowed (although happy to hear other opinions).
As a user of elm-test it's not immediately clear to me why such a combination should be invalid. In my case I happened to have a test module called Json and a describe of Json, because this was just for a very brief demo of some Elm stuff to someone. However, if there are technical reasons why such a combination is invalid then I think that would be fine as long as it's documented, and the error message is better, like you say. Thanks!
If you have a test module called
Foo
you can't useFoo
as the string argument todescribe
. And, if you do, you get a misleading error message: "The test 'Foo' contains a child test of the same name. Let's rename them so we know which is which"Sample code:
This is also discussed in #493.
The text was updated successfully, but these errors were encountered: