Hi, It can often be difficult to identify suitable tasks for new contributors who want to make a contribution but have no particular itch to scratch of their own. In the past, my thoughts have turned to the code coverage and a response along the lines of "Pick a class / package with low coverage and write some tests to increase it.".
I have generally held back from those sorts of suggestions because they struck me as more of a 'make work' task. As you may have noticed I have been working on the HttpParser unit tests over the last few days. This was prompted, as a result of the recent fqdn parsing issues, to ensure that the unit tests were covering all of the edge cases. While the fqdn parsing was fine, working on the unit tests to expand code coverage uncovered three related bugs in the handling of some error cases in the HTTP header parsing. In light of the above experience, I now think suggesting improving the unit test coverage is a great place to suggest for a contributor to get started when they don;t have their own itch to scratch. Thoughts? Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
