1. 15 May, 2017 1 commit
  2. 08 Mar, 2017 2 commits
  3. 16 Feb, 2017 2 commits
  4. 09 Feb, 2017 1 commit
    • anonym's avatar
      Test suite: let's see if the 'press' action is more reliable than .click(). · cf44cb39
      anonym authored
      The .click() method actually looks up the coordinates of the element
      and then clicks those coordinates. The 'press' action directly causes
      a "click" event that cannot be lost.
      
      The affected part has been failing quite regularly on Jenkins,
      presumably because the GUI isn't finished loading at the time, so the
      coordinates we end up clicking on (with .click()) are the wrong ones.
      cf44cb39
  5. 02 Feb, 2017 4 commits
  6. 31 Jan, 2017 1 commit
    • anonym's avatar
      Test suite: look for the expected email's subject column. · f0bfd4df
      anonym authored
      Previously we looked for the whole line, but calling .click will
      result in clicking in its middle which might be something that doesn't
      give focus, e.g. the column for the message status (whether it was
      read or not).
      f0bfd4df
  7. 30 Jan, 2017 1 commit
  8. 25 Jan, 2017 2 commits
    • anonym's avatar
      Add missing return value to try_for(). · 27370365
      anonym authored
      ... due to try_for()'s silly semantics.
      
      Refs: #9223
      27370365
    • 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
  9. 22 Dec, 2016 1 commit
  10. 11 Dec, 2016 1 commit
    • anonym's avatar
      Do not test sending email when testing POP3. · de0f1de6
      anonym authored
      We cannot clean that email up (easily) since when we use POP3 deletions
      won't affect the remote inbox, only our local one. Note that we already
      test SMTP in another scenario, so no test coverage is lost,
      really (unless SMTP works differently with POP3 compared to IMAP, which
      I think we can assume is not the case).
      
      Will-fix: #12006
      de0f1de6
  11. 28 Nov, 2016 1 commit
  12. 28 Oct, 2016 2 commits
  13. 19 Oct, 2016 4 commits
  14. 12 Sep, 2016 2 commits
  15. 03 Sep, 2016 4 commits
  16. 02 Sep, 2016 3 commits
  17. 01 Sep, 2016 1 commit
    • anonym's avatar
      Dogtailify existing Icedove tests. · 865f32a7
      anonym authored
      ... which incidentally fixes the issue we've had with some outdated test
      suite images for this feature, and a robustness issue in TorBirdy's
      settings dialog. :)
      
      Also, by removing the IMAP scenario, which has been broken ever since we
      enabled the autoconfiguration wizard, we fix another failure -- we'll
      reintroduce an updated version of it shortly.
      
      Will-fix: #11571, #11400
      865f32a7
  18. 15 Apr, 2016 1 commit
    • anonym's avatar
      Remove Scenario: Icedove will work over Tor. · ac10a9e5
      anonym authored
      It depends on check.tp.o reporting that we use Tor, but we do not when
      using Chutney. When we actually add usage tests of Icedove, we'll
      implicitly test this any way.
      ac10a9e5
  19. 27 Oct, 2015 1 commit
  20. 15 Oct, 2015 1 commit
  21. 09 Oct, 2015 1 commit
  22. 08 Oct, 2015 3 commits