Author: atagar Date: 2014-02-03 15:25:35 +0000 (Mon, 03 Feb 2014) New Revision: 26579 Modified: website/trunk/getinvolved/en/volunteer.wml Log: Dropping 'Stem Tests for Tor' Stem has pretty good tests and I'm not really sure where this project would go. It's presently a bit ill defined and Nick would rather use Chutney for tor testing. I'll give this some more though to see if there's something better defined we can propose. Modified: website/trunk/getinvolved/en/volunteer.wml =================================================================== --- website/trunk/getinvolved/en/volunteer.wml 2014-02-03 15:21:51 UTC (rev 26578) +++ website/trunk/getinvolved/en/volunteer.wml 2014-02-03 15:25:35 UTC (rev 26579) @@ -630,7 +630,6 @@ <p> <b>Project Ideas:</b><br /> <i><a href="#txtorcon-stemIntegration">Txtorcon/Stem Integration</a></i><br /> - <i><a href="#stemTestingForTor">Stem Tests for Tor</a></i> </p> <a id="project-txtorcon"></a> @@ -1008,37 +1007,6 @@ </p> </li> - <a id="stemTestingForTor"></a> - <li> - <b>Stem Tests for Tor</b> - <br> - Effort Level: <i>Medium</i> - <br> - Skill Level: <i>Medium</i> - <br> - Likely Mentors: <i>Damian (atagar)</i> - <p> - Stem is a library for interacting with Tor (see '<a href="#stemUsability">Stem Usability and Porting</a>' above for a summary). The library has both <a href="https://gitweb.torproject.org/stem.git/tree/HEAD:/test/unit">unit</a> and <a href="https://gitweb.torproject.org/stem.git/tree/HEAD:/test/integ">integration</a> tests. The unit tests provide a quick, direct test of stem's codebase while the integration test exercises its functionality against a live instance of Tor. - </p> - - <p> - Stem's integration tests have thus far been (unsurprisingly) designed to test stem but there's no need for them to be limited to that. Stem is a complete implementation of Tor's <a href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/control-spec.txt">control-spec</a> and <a href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/dir-spec.txt">dir-spec</a>. As such, stem's tests could be easily expanded to more dedicatedly test behavior involved in those portions of Tor's codebase, as well as provide a smoke test for its general functionality. - </p> - - <p> - This project would involve several components: - </p> - - <ol> - <li>Determine what kind of tests we need. <b>This should be done during the application phase</b> by <a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev/">contacting tor-dev@</a>. Hopefully this will give us an idea of what would be the most useful kind of tests of this nature for Tor development.</li> - <li>Our <a href="https://jenkins.torproject.org/job/stem-tor-ci/">automated testing environment</a> presently sends the test output when they fail. We should think about having our tests optionally provide html formatted results (maybe this is something a testing framework can already provide?).</li> - <li>Implement the new suite of integration tests for Tor. This will likely include expanding Tor to support better testability. One useful candidate, for instance, would be a controller method to fetch our own descriptor. This would let us easily test various configurations to see if they provide valid descriptor content.</li> - </ol> - - <p> - <b>As part of your application for this project please write some code to expand stem's tests.</b> Bonus points if it implements one of your suggestions for better testing Tor! - </p> - <a id="torCleanup"></a> <li> <b>Tor Codebase Cleanup</b>