1. 29 Jul, 2021 3 commits
  2. 28 Jul, 2021 1 commit
  3. 21 Jul, 2021 4 commits
  4. 05 Jun, 2021 1 commit
  5. 09 Mar, 2021 1 commit
  6. 05 Mar, 2021 1 commit
  7. 22 Jan, 2021 1 commit
    • anonym's avatar
      Test suite: adapt to Tor Launcher always starting (refs: #17330) · 60821e3f
      anonym authored
      I picked a rather transparent and implicit approach, by handing the
      default Tor Launcher case (direct connection) right in the `Tor is
      ready` step. This might be a bit opaque and confusing, however, but
      otherwise, in all scenarios/snapshots where we have:
      
          And the network is plugged
          ...
          Then Tor is ready
      
      we would have to add steps:
      
          And the network is plugged
          ...
          And the Tor Launcher autostarts
          When I configure a direct connection in Tor Launcher
          Then Tor is ready
      
      which is a bit spammy. I suppose it could be compressed into:
      
          And the network is plugged
          ...
          Then Tor is ready after I choose a direct connection in Tor Launcher
      
      but I don't like that kind of formulations in Gherkin.
      60821e3f
  8. 23 Apr, 2020 1 commit
    • intrigeri's avatar
      Test suite: improve Gherkin · 073d92ba
      intrigeri authored
      Scenario names are supposed to concisely describe the desired behavior
      of the system under test, rather than the steps required to perform
      the actual tests.
      073d92ba
  9. 11 Jul, 2019 2 commits
  10. 17 Nov, 2018 1 commit
  11. 22 May, 2017 1 commit
  12. 15 Mar, 2017 1 commit
  13. 22 Jul, 2016 1 commit
  14. 14 May, 2016 2 commits
    • anonym's avatar
      Remove most scenarios testing "tordate". · ffba63de
      anonym authored
      "tordate" just isn't working well in Tails, so we shouldn't expect the
      tests to actually work all of the time. The two tests we keep will at
      least ensure that "tordate" doesn't break the (presumably) most common
      situation, where the hardware clock is correct.
      
      Refs: #10440
      ffba63de
    • anonym's avatar
      Fix indentation. · 35f3afe2
      anonym authored
      35f3afe2
  15. 20 Apr, 2016 1 commit
  16. 20 Feb, 2016 1 commit
  17. 07 Dec, 2015 1 commit
  18. 28 Oct, 2015 1 commit
  19. 06 Oct, 2015 2 commits
  20. 02 Oct, 2015 2 commits
  21. 28 Jun, 2015 1 commit
  22. 27 Jun, 2015 2 commits
  23. 15 May, 2015 2 commits
  24. 12 May, 2015 2 commits
    • anonym's avatar
      Remove the impossible "Clock way in the past" scenarios. · 394fcf50
      anonym authored
      Thanks to
      
          config/chroot_local-includes/lib/live/config/0001-sane-clock
      
      these scenarios cannot happen, and since we test that it works they
      can be safely removed.
      394fcf50
    • anonym's avatar
      Test the system clock sanity check we do at boot. · f9658a9f
      anonym authored
      I.e. check that
      
          config/chroot_local-includes/lib/live/config/0001-sane-clock
      
      does what it's supposed to, which is to ensure that the system clock
      cannot be set before the Tails build date (if so, we set it to the
      Tails build date).
      
      Will-fix: #9377
      f9658a9f
  25. 05 May, 2015 1 commit
  26. 19 Feb, 2015 1 commit
  27. 03 Feb, 2015 1 commit
  28. 03 Oct, 2014 1 commit