1. 21 Jan, 2017 1 commit
  2. 17 Nov, 2016 1 commit
  3. 21 Jul, 2016 1 commit
  4. 11 May, 2016 2 commits
  5. 26 Apr, 2016 1 commit
    • anonym's avatar
      Make sure @lan_hosts is initialized. · 8474c250
      anonym authored
      That should never be a problem since it's initialized in a Before
      hook. While that is worrying, it still makes sense to have this
      initialization outside of the Before hook so hooks run before it could
      use this function.
  6. 22 Apr, 2016 1 commit
  7. 20 Apr, 2016 1 commit
    • anonym's avatar
      Completely rewrite the firewall leak detector. · c2a2465c
      anonym authored
      The old design was very inflexible, which over time lead to the
      implementation growing messy as different checks were added. The
      issue was that it had to hard-code the particular checks we
      wanted, and did not allow the user to formulate an expression for
      which packets are considered leaks or not. So, let's instead
      provide an assertion-like function to which the user passes a
      block describing how we want all our packets to look.
      Furthermore, now all firewall leak tests should be ok with the
      simulated Tor network provided by Chutney. Since all Tor nodes
      (incl. bridges) run from the same host (and IP address) we also
      include the server port when verifying that no unexpected hosts were
      Note that in some cases we've lost a bit of information and
      precision, e.g. among the anti-tests we no longer exactly match
      the protocol that was leaked, but that wasn't very valuable to
      begin with, and instead we test *exactly* the code that these are
      anti tests for -- a true anti test, indeed!
      Also, the 'no traffic has flowed to the LAN' (now renamed) had a
      serious bug which was fixed in passing -- the `@lan_host`
      variable was not set, so it is `nil`, which could never be among
      the IPv4 TCP leaks, so that step always succeeded! :S
  8. 19 Apr, 2016 1 commit
    • anonym's avatar
      Make Chutney obligatory. · 3c247296
      anonym authored
      This will just make things simpler. So long, real Tor network, and
      thanks for all the fish! :)
  9. 18 Apr, 2016 1 commit
    • anonym's avatar
      Be less smart about starting Chutney. · 5b5f049a
      anonym authored
      If we are restoring a snapshots from a previous run (with
      --keep-snapshots) where Chutney already has been set up, and where the
      network is not plugged, and then we plug the network, then Chutney
      will not start at all according to the current logic, because it's
      only ensured to be running when restoring from a snapshot where the
      network already was plugged.
      So, let's just ensure Chutney is running before each @product feature,
      even if it won't be used at all.
  10. 09 Feb, 2016 1 commit
  11. 05 Feb, 2016 3 commits
  12. 19 Dec, 2015 2 commits
  13. 07 Dec, 2015 1 commit
  14. 19 Nov, 2015 1 commit
  15. 14 Oct, 2015 1 commit
  16. 13 Oct, 2015 5 commits
  17. 06 Oct, 2015 9 commits
    • anonym's avatar
      Use a homebrew mktmpdir instead. · f7d43c20
      anonym authored
      The names of directories generated Dir.mktmpdir are pretty ugly. It
      includes today's date, which is good, but then it includes the
      PID. The date would be much more practical than the PID since then
      lexical sorting implies chronological sorting. So let's do that
    • anonym's avatar
      Add the --artifacts-base-url option to run_test_suite. · 5a2e1018
      anonym authored
      Will-fix: #10151
    • anonym's avatar
      Log useful information via Cucumber's formatters. · 1284f3ad
      anonym authored
      By writing to stderr such information is not logged to files when
      using `--out`, but when writing to stdout (which `puts` does by
      default) the human-readable formatters often do something smart (at
      least 'pretty' and 'debug' do, which are the ones we care most about).
      We only continue writing to stderr for the output of the options that
      requires interaction, i.e. --retry-find and --pause-on-fail.
      Will-fix: #10342
    • anonym's avatar
      Don't print which ISOs were testing. · e951ab15
      anonym authored
      We ought to know which ISOs we use from the command line. And we
      certainly do not need to print them for every feature, like we did.
      Besides, there's no good way for us to print this only once at the
      start so that cucumbers formatters would pick it up. At best we could
      print it right before the first "Scenario: ..." instance, but that
      seems ugly.
    • anonym's avatar
      Improve variable name. · b8d04c27
      anonym authored
    • anonym's avatar
      Delete an empty artifact directory on exit. · 759914f5
      anonym authored
    • anonym's avatar
      Ensure that the original pcap file is removed. · 45031ea9
      anonym authored
      When we want to keep it, we copy it and remove the original (awkward,
      but a fix would be a bit too involved for a drive-by fix in this
      branch). Without this fix, the original will be kept as well in the
      event of an error.
    • anonym's avatar
      Print time of error a bit later. · fa228f0b
      anonym authored
      This way we'll group the artifact paths better. The issue is with
      Sniffer's save_pcap_file method, which will print it before throwing
      the exception that fails the scenario, so the runtime ends up in the
      middle of these paths.
    • anonym's avatar
      Save all test suite artifacts in a dedicated directory. · 7dd7582d
      anonym authored
      This makes it easier to see what belongs to which run. While we're at
      it we also improve the names so they actually refer to the scenario
      that failed.
      Will-fix: #10151
  18. 15 Sep, 2015 5 commits
  19. 10 Sep, 2015 2 commits