1. 24 Jun, 2013 2 commits
    • When an assertion fails, casperjs stops any steps in the current suite.
      This could cause issues in a test suite. For example, "withFrame"
      generates some steps:
      
      - one to switch to the given frame
      - one to execute the given tests
      - one to switch to the main frame.
      
      If tests fail, the third step is not executed, and then next tests fail
      because they are not executed in the main frame.
      
      we can saw this issue in selftests: if a test fails in tests/suites/casper/frame.js,
      tests in tests/suites/casper/global.js fail too.
      Laurent Jouanneau authored
    • Laurent Jouanneau authored
  2. 21 Jun, 2013 1 commit
  3. 20 Jun, 2013 4 commits
  4. 18 Jun, 2013 2 commits
  5. 13 Jun, 2013 1 commit
  6. 09 Jun, 2013 4 commits
  7. 08 Jun, 2013 1 commit
  8. 07 Jun, 2013 1 commit
    • The call of webpage.open() (or openUrl()) is synchronous in PhantomJS,
      but is asynchronous in SlimerJS (it needs to open a real window etc..).
      
      So CasperJS should not launch the next step just after the call of
      webpage.openUrl(). A flag is set to true before this call, and
      then set to false when receiving the first event from the page loader.
      And this flag has to be checked before to execute the next step.
      Laurent Jouanneau authored
  9. 04 Jun, 2013 1 commit
  10. 02 Jun, 2013 4 commits
  11. 28 May, 2013 1 commit
  12. 27 May, 2013 4 commits
  13. 23 May, 2013 2 commits
  14. 22 May, 2013 1 commit
  15. 21 May, 2013 4 commits
  16. 13 May, 2013 2 commits
  17. 12 May, 2013 1 commit
  18. 10 May, 2013 1 commit
  19. 09 May, 2013 3 commits