[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 trygve):
Proof of concept test for the BridgeDB web interface attached, written in
Python. The test opens the BridgeDB web page on the local host, follows
the 'bridges' link to '/options', modifies one of the 'advanced options',
submits the form and inputs the correct value in the captcha. It then goes
on to verify that at least one bridge line of the correct form is
returned.
The ticket suggested the use of Windmill, twill or zope.testbrowser for
testing the web interface.
For the proof of concept, I've used the mechanize and BeautifulSoup
libraries because I've worked with them before. Note that both twill and
zope.testbrowser are actually wrappers around mechanize
(http://wwwsearch.sourceforge.net/mechanize/)
Note: the proof of concept does not use Twisted's trial. If the test is
reviewed and found to be helpful, I can update it be consistent with the
rest of the test, and add a number of additional tests to exercise more of
the BridgeDB code.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9874#comment:7>
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