1. 08 Mar, 2017 5 commits
  2. 28 Feb, 2017 1 commit
    • anonym's avatar
      Completely remove I2P. · e9d02049
      anonym authored
      We have decided to remove I2P (Refs: #11276) due to our failure of
      finding someone interested in maintaining it in Tails.
      
      Will-fix: #12263
      e9d02049
  3. 31 Jan, 2017 1 commit
  4. 25 Jan, 2017 1 commit
    • anonym's avatar
      Dogtail: use the remote shell's new Python session feature. · 1558f125
      anonym authored
      ... to significantly improve Dogtail's performance by saving state and
      reusing it between Dogtail commands.
      
      This is a massive commit, and it changes the semantics of the creation
      of Dogtail objects. Previously they just created the code that then
      would be run once an actionable method was called (.wait, .click etc),
      but now it works like in Python, that Dogtail will try to find the
      graphical element upon object creation.
      
      Will-fix: #12059
      1558f125
  5. 22 Jan, 2017 2 commits
  6. 28 Nov, 2016 1 commit
  7. 16 Nov, 2016 1 commit
  8. 29 Aug, 2016 1 commit
  9. 30 May, 2016 2 commits
  10. 21 May, 2016 3 commits
    • anonym's avatar
      Simplify step name. · 07c8c4eb
      anonym authored
      07c8c4eb
    • anonym's avatar
      Fix multiple issues with dogtail waiting for a browser page to load. · c1bcba2e
      anonym authored
      Also, this is a great simplification. :)
      
      It turns out the previous code had multiple errors (symbol error
      because of True when it should be true, no .wait so the generated
      python code was never run) but even after fixing them I learned that
      try_for and assert_raise doesn't work together because it will catch
      try_for's timeout exception. Even when telling assert_raise to look
      for a specific exception it will still catch the other ones and then
      interpret them as an assertion failure, so the try_for never
      halts. Yay. It should be possible to get an ~assert_raise that we need
      here with some begin-rescue logic, but let's not bother.
      c1bcba2e
    • anonym's avatar
      Dogtailify step. · d014c7c6
      anonym authored
      This step was broken due to Tor Browser 6.0.x changing the zoom-levels
      (or similar) so various elements of the just removed image were not
      positioned the way we expected them.
      d014c7c6
  11. 11 May, 2016 2 commits
    • anonym's avatar
      Drop the usage of Tor Check in our tests. · e500661b
      anonym authored
      It doesn't make sense now when we use Chutney since that always means
      it will report that Tor is not being used.
      
      In some scenarios we used it simply because we needed *some* page
      (distinct from the Tails News page) and we had the image. In those
      cases we now use the Tails homepage instead. I tried to use dogtail,
      but realized that dogtail won't work for the Unsafe Browser due to
      e500661b
    • anonym's avatar
      77d16ece
  12. 15 Apr, 2016 1 commit
  13. 14 Apr, 2016 1 commit
  14. 10 Feb, 2016 1 commit
  15. 09 Feb, 2016 2 commits
    • anonym's avatar
      Move tor-launcher-standalone into /usr/local/lib. · 06bc2513
      anonym authored
      ... where we have the Tor Browser. For consistency.
      06bc2513
    • anonym's avatar
      Make the -profile Tor Launcher workaround simpler. · 2db6d171
      anonym authored
      ... instead of the crazy workaround we had to use before. It turns out
      you *can* use -app and -profile together, but only if -profile is
      given last. It may be that it was fixed recently, because I'm pretty
      sure it didn't work last time I wroked on this.
      
      Also, in /usr/share/TorBrowser/Data/Browser (which is the "default"
      profile directory relative to the Tor Launcher applocation.ini file)
      the Caches directory must exist and be accessible for the tor-launcher
      user even if -profile is used, so we just have to ensure it exists.
      
      Will-fix: #7943
      2db6d171
  16. 09 Jan, 2016 1 commit
    • intrigeri's avatar
      Tor Browser download test: explicitly wait for the "Save as" button. · 9aecc39e
      intrigeri authored
      We were waiting for the dialog (BrowserDownloadDialog.png) to show up, and then
      clicking on a button that is part of that dialog
      (BrowserDownloadDialogSaveAsButton.png). In the past we've seen such
      implementations be fragile, due to race conditions between when all the widgets
      in a window are drawn vs. when Sikuli notices the first ones appear.
      
      So, let's consider that "I get the browser download dialog" really means "I get
      the browser download dialog including all its widgets that we are really
      interested in".
      
      refs: #9285
      9aecc39e
  17. 08 Jan, 2016 1 commit
  18. 29 Nov, 2015 1 commit
  19. 18 Nov, 2015 1 commit
  20. 17 Nov, 2015 1 commit
    • anonym's avatar
      Work around issue with lost key presses in the browser. · 5052b4c6
      anonym authored
      When entering an address like"http(s)" we sometime end up with
      "htp(s)", so either the second or third character is lost. My guess is
      the second; once the first character is entered, the Tor Browser
      immediately starts showing the list of suggestions, and it seems if
      the second character is timed at some particular point when this list
      is being shown, it's lost.
      
      This is worked around by just pasting the whole address in one go, via
      the clipboard.
      
      Will-fix: #10467
      5052b4c6
  21. 11 Nov, 2015 2 commits
  22. 30 Oct, 2015 1 commit