Clarify test discovery docs.

[avojnovicDk]

Thanks for submitting a PR, your contribution is really appreciated!

Here's a quick checklist that should be present in PRs:

• Target: for bug or doc fixes, target master; for new features, target features;

Unless your change is trivial documentation fix (e.g., a typo or reword of a small section) please:

• Make sure to include one or more tests for your change;
• Add yourself to AUTHORS;
• Add a new entry to CHANGELOG.rst
  • Choose any open position to avoid merge conflicts with other PRs.
  • Add a link to the issue you are fixing (if any) using RST syntax.
  • The pytest team likes to have people to acknowledged in the CHANGELOG, so please add a thank note to yourself ("Thanks @user for the PR") and a link to your GitHub profile. It may sound weird thanking yourself, but otherwise a maintainer would have to do it manually before or after merging instead of just using GitHub's merge button. This makes it easier on the maintainers to merge PRs.

[coveralls]

Coverage remained the same at 92.819% when pulling 2e6a58a on avojnovicDk:issue-1808 into 33796c8 on pytest-dev:master.

[nicoddemus]

Thanks! Your version does read better!

I'm re-triggering AppVeyor because the failed job seems to be a fluke. As soon as it passes I'll merge this.

[nicoddemus]

Actually it does not seem to be a fluke, I will investigate it.

[nicoddemus]

Not a fluke, but unrelated to this PR: pypa/setuptools#861

[nicoddemus]

I tested locally your PR merged with #2092 and it passes, so I'm merging this.

Thanks again!

[decentral1se]

🚀