In general the answer to helping with code coverage is "whatever module motivates you to help". :) So unless a core dev has a specific module that they want to help you write tests for then it's whatever you want to work on.
And for easy reference, the code coverage report can be found at https://codecov.io/gh/python/cpython (although it is somewhat inaccurate for any module imported at startup). On Mon, 10 Jul 2017 at 07:54 Artem Muterko <arti...@gmail.com> wrote: > Good day, > > I've noticed that test coverage of standard library tools can be improved > and wanted to ask which module is better to start with? > > I'm kindly asking to point to the module which would be good to start > writing tests for and also easy to review for other contributors. > > Best regards, > Artem Muterko > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/brett%40python.org >
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
