Not really. It's is checking that the function that generates the message
is actually called. The test doors check application logic.

Dave
On Dec 20, 2013 5:51 PM, "Eric Meadows-Jönsson" <notifications@github.com>
wrote:

> In lib/mix/lib/mix/tasks/deps.check.ex:
>
> > @@ -58,4 +68,8 @@ defmodule Mix.Tasks.Deps.Check do
> >        end)
> >      end
> >    end
> > +
> > +  # DRY up tests
> > +  def cant_continue_message,
> > +  do: "Can't continue: there were errors in the dependencies"
>
> It is duplicated so we can make sure that the error message is correct. If
> someone makes a mistake in cant_continue_mistake the test will not catch
> the erroneous error message.
>
> If it is not important to test the error message, we can change the test
> to not check it:
>
> assert_raise Mix.Error, fn ->
>   Mix.Tasks.Deps.Check.run []end
>
> As it is now is sort of like checking that foo() == foo().
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/elixir-lang/elixir/pull/1951/files#r8514754>
> .
>