[python-committers] Codecov and PR
Terry Reedy
tjreedy at udel.edu
Thu Apr 27 02:51:46 EDT 2017
More information about the python-committers mailing list
Thu Apr 27 02:51:46 EDT 2017
- Previous message (by thread): [python-committers] Codecov and PR
- Next message (by thread): [python-committers] Codecov and PR
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 4/27/2017 1:52 AM, Ethan Furman wrote: > On 04/26/2017 10:35 PM, Terry Reedy wrote: >> On 4/26/2017 1:45 PM, Brett Cannon wrote: > >>> :) But they are at least executed which is what we're really >>> measuring here and I think all Ethan and I are advocating >>> for. >> >> I thought Ethan was advocating for more -- a specific unittest for >> each line. > > I'm hoping that's just poor wording, or each module would need hundreds > of tests. ;) Poor wording, but I was wrong in any case. An aspirational goal is that each line of of each function be exercised for correctness by at least one unittest. For top-level code not in a function or class, we mostly have to settle for compile and run without error.
- Previous message (by thread): [python-committers] Codecov and PR
- Next message (by thread): [python-committers] Codecov and PR
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list