Skip to content

Commit 3d80b68

Browse files
committed
Update the ReadMe
1 parent 26b3708 commit 3d80b68

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -384,10 +384,10 @@ nosetests test_suite.py --firefox
384384
385385
<p><code>pytest</code> includes automatic test discovery. If you don't specify a specific file or folder to run, <code>pytest</code> will automatically search through all subdirectories for tests to run based on the following criteria:</p>
386386
387-
* Python files that start with ``test_``.
387+
* Python files that start with ``test_`` or end with ``_test.py``.
388388
* Python methods that start with ``test_``.
389389
390-
With a SeleniumBase [pytest.ini](https://github.com/seleniumbase/SeleniumBase/blob/master/examples/pytest.ini) file present, (which modifies default discovery settings), files that end with ``_test.py`` will also be discovered automatically. The Python class name can be anything because SeleniumBase's ``BaseCase`` class inherits from the ``unittest.TestCase`` class.
390+
With a SeleniumBase [pytest.ini](https://github.com/seleniumbase/SeleniumBase/blob/master/examples/pytest.ini) file present, you can modify default discovery settings. The Python class name can be anything because ``seleniumbase.BaseCase`` inherits ``unittest.TestCase``, which triggers autodiscovery.
391391
392392
<p>✅ You can do a pre-flight check to see which tests would get discovered by <code>pytest</code> before the real flight:</p>
393393

0 commit comments

Comments
 (0)