1. 07 Feb, 2017 2 commits
  2. 15 Jun, 2015 1 commit
  3. 28 Nov, 2014 2 commits
  4. 24 Nov, 2014 1 commit
  5. 18 Feb, 2014 1 commit
    • Emilio Pozuelo Monfort's avatar
      tests: Properly report skipped tests · dae8a4b9
      Emilio Pozuelo Monfort authored
      We were calling exit(0) when tests were skipped, which counted
      them as passed instead of skipped. Fix this by properly exiting
      with 77 (which is what automake expects for skipped tests) from
      the tests themselves, then returning 77 again from weston-test-runner
      if all the tests were skipped. Finally the weston-test.so module
      catches weston-test-runner's exit code and uses it as an exit code,
      which is what automake will see and use.
      Signed-off-by: default avatarEmilio Pozuelo Monfort <emilio.pozuelo@collabora.co.uk>
  6. 13 Sep, 2013 1 commit
    • Sam Spilsbury's avatar
      Add support for table-driven testing. · b502126e
      Sam Spilsbury authored
      The new TEST_P macro takes a function name and a "data" argument to
      point to an arbitrary array of known size of test data. This allows
      multiple tests to be run with different datasets. The array is stored
      as a void * but advanced by a known size on each iteration.
      The data for each invocation of the test is provided as a "data" argument,
      it is the responsibility of the test to cast it to something sensible.
      Also fixed single-test running to only run the tests specified
  7. 11 Sep, 2013 3 commits
  8. 24 Jan, 2013 1 commit
    • Pekka Paalanen's avatar
      tests: make signal other than ABRT a hard failure · 585c27c7
      Pekka Paalanen authored
      We handle FAIL_TEST tests by simply inverting the success flag. The
      problem with this is, that if a FAIL_TEST fails by a SIGSEGV, it will be
      interpreted as passed. However, no code should ever cause a SEGV, or any
      other signal than ABRT. And even ABRT only in the case of an assert()
      that is meant to fail. We would probably need more sophistication for the
      FAIL_TEST cases.
      For now, just interpret any other signal than ABRT as a hard failure,
      regardless whether it is a TEST or FAIL_TEST. At least segfaults do not
      cause false passes anymore.
      Signed-off-by: Pekka Paalanen's avatarPekka Paalanen <ppaalanen@gmail.com>
  9. 11 Dec, 2012 1 commit