1. 10 Apr, 2015 2 commits
    • anonym's avatar
      Actually run a web server on the LAN. · 709c9c75
      anonym authored
      It shouldn't be needed for the Tor Browser test since we check the
      network traffic, but we'll need it when testing the Unsafe Browser, so
      why not?
    • anonym's avatar
      Test that the Tor Browser cannot access LAN resources. · 1d27515e
      anonym authored
      Since no HTTP server is listening on the LAN resource the Tor Browser
      would show the same "Unable to connect" error message even if the
      request wasn't blocked. We should be fine, though, since we check the
      captured traffic. The picture is more of a signal saying that "now the
      network traffic would have been generated *if* the request isn't
      blocked" which we use to know when to check the network capture.
  2. 18 Feb, 2015 1 commit
  3. 12 Feb, 2015 1 commit
    • Tails developers's avatar
      Reorder steps to avoid lost key presses. · 4d985860
      Tails developers authored
      First we start the Tor Browser, then we run the step 'there is a GNOME
      bookmark for the amnesiac Tor Browser directory' which opens the GNOME
      Places menu. It seems this may cause the Ctrl+S key presses in the
      next step 'I can save the current page as "index.html" to the default
      downloads directory' to not reach the Tor Browser, but probably get
      lost in the Places menu before it closes from the Esc key press
      (Sikuli is fast!), so the step fails. The new step ordering prevents
      this from happening.
  4. 10 Feb, 2015 1 commit
  5. 06 Feb, 2015 1 commit
    • Tails developers's avatar
      WIP: Rename the Tor Browser "download" directory, again. And add automated... · 136db50c
      Tails developers authored
      WIP: Rename the Tor Browser "download" directory, again. And add automated tests for the Tor Browser.
      The idea is to make sure that the AppArmor confinement doesn't break too much
      functionality, and actually confines the browser a bit.
      Sorry for the non-atomic commit: getting directory name changing under my feet
      while the automated tests are being drafted made it too hard to split this in
      a nice way.
  6. 03 Feb, 2015 1 commit
  7. 30 Jan, 2015 1 commit
  8. 02 Oct, 2014 1 commit
  9. 24 Sep, 2014 1 commit
    • Tails developers's avatar
      Fix automated test suite for migration to TBB. · 8c176bbb
      Tails developers authored
      Beyond s/Iceweasel/Tor Browser/ (incl. renaming affected images) we
      also try to rely more on clicking on GUI elements instead of keyboard
      shortcuts. The TBB is noticeably slower on start, and often loses key
      presses at that stage, so clicking is much more reliable then.
      The most remarkable change may be the switch to the step "the Tor
      Browser has started and loaded the startup page". It seems a fair
      amount of complexity is required to reliably stop the loading of the
      startup page so this simpler approach seems better, and as a bonus it
      actualy tests the startup page. The issue described in the removed
      comment doesn't seem very relevant any more, too.
  10. 12 Aug, 2014 1 commit
  11. 08 Apr, 2014 1 commit
  12. 04 Mar, 2014 4 commits
  13. 02 Mar, 2014 1 commit
  14. 22 Feb, 2014 1 commit
  15. 07 Jan, 2014 1 commit
  16. 30 Mar, 2013 1 commit
  17. 28 Mar, 2013 2 commits
  18. 27 Mar, 2013 1 commit
    • Tails developers's avatar
      Reorganise features/, unifying both test suites. · 375216ce
      Tails developers authored
      Now all .feature:s reside directly in the root of features/, and they
      are differentiated with tags: source tests are tagged '@source' and
      product (i.e. Tails ISO image) tests are tagged '@product'. These tags
      then set up the appropriate environment on a feature-by-feature basis.
  19. 08 Mar, 2013 1 commit
  20. 26 Feb, 2013 1 commit
  21. 25 Jan, 2013 5 commits
  22. 31 Oct, 2012 1 commit
  23. 30 Oct, 2012 1 commit
  24. 23 Jun, 2012 1 commit
  25. 19 Jun, 2012 1 commit
  26. 17 Jun, 2012 1 commit