[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):

 For one, I should state something I realised nearly a year ago so that no
 one else makes the same mistake: you [https://github.com/isislovecruft
 /tor-browser-selenium can't drive TorBrowser with Selenium], because
 Selenium can't touch XUL elements. So while using Selenium would likely
 still work for testing all the major browsers for BridgeDB's HTTP(S) user
 interface, it wouldn't work for automated testing of BridgeDB's HTTP(S) UI
 in TorBrowser. We'll likely need both, in some capacity or another,
 because BridgeDB
 [https://gitweb.torproject.org/bridgedb.git/blob/HEAD:/lib/bridgedb/Main.py#l366
 behaves differently if it believes that you're coming from a Tor exit
 relay] (and we want to ensure that it ''is'' behaving differently for Tor
 and non-Tor users).

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9874#comment:4>
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