[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #9874 [BridgeDB]: Research/design a way to automate testing of BridgeDB's HTTPS and email distributors

#9874: Research/design a way to automate testing of BridgeDB's HTTPS and email
distributors
-------------------------+-------------------------------------------------
     Reporter:  isis     |      Owner:  isis
         Type:           |     Status:  needs_information
  enhancement            |  Milestone:
     Priority:  normal   |    Version:
    Component:           |   Keywords:  bridgedb-unittests, automation, ci,
  BridgeDB               |  bridgedb-gsoc-application
   Resolution:           |  Parent ID:
Actual Points:           |
       Points:           |
-------------------------+-------------------------------------------------

Comment (by isis):

 And... more things I've forgotten to mention on this ticket.

 When testing BridgeDB, the usual way to run the tests (after installing
 and configuring BridgeDB and all its dependencies) is with Twisted's
 `trial`, by doing:

 {{{
 .../bridgedb/ $ trial ./lib/bridgedb/test/test_*.py
 }}}

 To obtain fake bridge descriptors for testing, use the
 [https://pypi.python.org/pypi/leekspin leekspin] module I wrote to
 generate them. (It requires [https://pypi.python.org/pypi/pyOpenSSL
 pyOpenSSL] and, optionally, [https://pypi.python.org/pypi/PyNaCl pyNaCl],
 though the latter only if you want to generate `ntor-onion-key`s in the
 fake bridges' descriptors.)

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9874#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs