Terminal writing with a single test produces "collected 1 item s"
See original GitHub issueI’m using Terminal
in ubuntu 16.04
The pytest versions are listed in the screenshot. My repository contains a single test.
I did some debugging work and it does seem it is placing the \r
characters properly (to clear the line) but it doesn’t seem to be clearing the entire contents (leaving artifacts from the previous writes).
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
'pytest' exits with no error, but with "collected 0 items"
I wrote a unit test for this module (with a simple assert statement to check equality of lists) where I first instantiate the...
Read more >Incorrect number of collected items reported when specific ...
In a simple example (see below) when we want to collect/run only one specific test method from a class, one expects to get...
Read more >Managing pytest's output — pytest documentation
Each test inside the file is shown by a single character in the output: . for passing, F for failure. test_words_fail failed, and...
Read more >Running Tests with pytest - The Carpentries Incubator
With pytest, this is the command-line tool called pytest . When pytest is run, it will search all directories below where it was...
Read more >pytest Documentation - Read the Docs
Each collected test is assigned a unique nodeid which consist of ... One of the things that makes pytest's fixture system so powerful,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ah cool, #2579 looks like an exact dupe, I’ll follow that issue instead!
i see now - #2579 records that the issue wasnt solved