Browse code

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.

Damian Johnson authored on03/02/2014 16:25:35
Showing1 changed files
... ...
@@ -630,7 +630,6 @@ meetings around the world.</li>
630 630
     <p>
631 631
     <b>Project Ideas:</b><br />
632 632
     <i><a href="#txtorcon-stemIntegration">Txtorcon/Stem Integration</a></i><br />
633
-    <i><a href="#stemTestingForTor">Stem Tests for Tor</a></i>
634 633
     </p>
635 634
 
636 635
     <a id="project-txtorcon"></a>
... ...
@@ -1008,37 +1007,6 @@ meetings around the world.</li>
1008 1007
     </p>
1009 1008
     </li>
1010 1009
 
1011
-    <a id="stemTestingForTor"></a>
1012
-    <li>
1013
-    <b>Stem Tests for Tor</b>
1014
-    <br>
1015
-    Effort Level: <i>Medium</i>
1016
-    <br>
1017
-    Skill Level: <i>Medium</i>
1018
-    <br>
1019
-    Likely Mentors: <i>Damian (atagar)</i>
1020
-    <p>
1021
-    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.
1022
-    </p>
1023
-
1024
-    <p>
1025
-    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.
1026
-    </p>
1027
-
1028
-    <p>
1029
-    This project would involve several components:
1030
-    </p>
1031
-
1032
-    <ol>
1033
-      <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>
1034
-      <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>
1035
-      <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>
1036
-    </ol>
1037
-
1038
-    <p>
1039
-    <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!
1040
-    </p>
1041
-
1042 1010
     <a id="torCleanup"></a>
1043 1011
     <li>
1044 1012
     <b>Tor Codebase Cleanup</b>