1. 03 Apr, 2019 6 commits
  2. 02 Apr, 2019 25 commits
  3. 25 Mar, 2019 2 commits
    • intrigeri's avatar
      Test suite: clarify what WebM scenarios are fragile (refs: #10442) · 8a978562
      intrigeri authored
      There's been some confusion going on wrt. #10442 and WebM test cases.
      AFAICT, currently:
      
      1. Browsing the web using the Tor Browser → Watching a WebM video: I don't think
         it's fragile anymore. At least it hasn't failed in the last 5 full test suite
         runs on the stable branch. Let's re-enable it and if it proves to still be
         fragile, mark it as such and reference a new, dedicated ticket.
      
      2. Using Totem → Watching a WebM video over HTTPS: well, it's not just
         "fragile", it fails (almost?) every single time on lizard these days.
         That's what #10442 is about, let's make this clear in the test suite.
      8a978562
    • intrigeri's avatar
      Test suite: disable tests about notifications in case of MAC spoofing failure (refs: #10774) · 87663631
      intrigeri authored
      These notifications are not always displayed, which seems to be a real bug
      and not a test suite robustness issue. This bug has been here for more
      than three years. In the last 5 full test suite runs on the stable branch,
      these steps failed 5/3×5 = 40% of the time. This does not give us any
      useful information, other than confirming the bug, so let's drop these steps,
      which incidentally allows us to remove the @fragile tags on the corresponding
      scenarios ⇒ greater chances we detect issues in the "fail closed" property,
      which is great.
      87663631
  4. 23 Mar, 2019 7 commits