Closed
Description
In the cookbook article How to create a Console Command there is a section on Testing Commands.
This section is a little vague on details and should be expanded upon to be a bit more friendly. Some ideas for improvement:
Application should be used instead of Application:
- This currently only links to the two separate classes and is very confusing on first read because you have to click each respective link to find out which one to NOT use. Instead detail which package each one is from and explain WHY this suggestion is being made.- Reading that extending from
WebTestCase
was the best way to test my command is a bit weird. I think, "My Command has nothing to do with the web--why am I extending from a class called WebTestCase?" To me this sounds likeSymfony\Bundle\FrameworkBundle\Test\WebTestCase
should be renamed to something more generic likeFunctionalTestCase
.
I have opened a PR about renaming WebTestCase
to FunctionalTestCase
: symfony/symfony#7704
Metadata
Metadata
Assignees
Labels
Clear and specific issues ready for anyone to take them.Clear and specific issues ready for anyone to take them.Ideal for your first contribution! (some Symfony experience may be required)Ideal for your first contribution! (some Symfony experience may be required)