1. 28 Apr, 2015 2 commits
  2. 21 Apr, 2015 1 commit
  3. 14 Apr, 2015 1 commit
  4. 13 Apr, 2015 3 commits
  5. 10 Apr, 2015 3 commits
  6. 09 Apr, 2015 3 commits
    • Pekka Paalanen's avatar
      tests: add ivi_layout stand-alone test module · 46804ca5
      Pekka Paalanen authored
      This is the ivi_layout stand-alone test controller module that does not
      require any clients to run. Therefore it is much simpler than
      ivi_layout-test-plugin.c and does not need a matching part in
      Signed-off-by: Pekka Paalanen's avatarPekka Paalanen <pekka.paalanen@collabora.co.uk>
      Reviewed-by: default avatarDerek Foreman <derekf@osg.samsung.com>
    • Pekka Paalanen's avatar
      tests: ivi_layout test infrastructure · f5b74f7d
      Pekka Paalanen authored
      Testing the ivi_layout API requires two things:
      - the tests must be written as a controller module to access the API
      - the tests need a helper client to create some objects that can then be
        managed via the API
      This patch adds all the infrastructure and two different kinds of
      example tests.
      Internal ivi-shell (ivi_layout) API tests are listed as ivi-*.la files
      in TESTS in Makefile.am. Weston-tests-env detects these, and runs Weston
      with ivi-shell, and loads the given module as a controller module, not
      as a normal plugin.
      The test controller module ivi-*.la will launch a helper client. For
      ivi-layout-test.la the helper client is ivi-layout.ivi.
      The helper client uses the weston-test-runner framework to fork and exec
      each TEST with a fresh connection to the compositor.
      The actual test is triggered by the weston_test_runner protocol
      interface, a new addition to weston-test.xml. The helper client uses
      weston_test_runner to trigger a test, and the server side of the
      interface is implemented by the test controller module
      The server side of weston_test_runner uses the same trick as
      weston-test-runner.h to gather a list of defined tests. A test is
      defined with the RUNNER_TEST macro.
      If a test defined by RUNNER_TEST succeeds, an event is sent to the
      helper client that it can continue (or exit). If a test fails, a fatal
      protocol error is sent to the helper client.
      Once the helper client has iterated over all of its tests, it signals
      the batch success/failure via process exit code. That is cought in the
      test controller module, and forwarded as Weston's exit code.
      In summary: each ivi_layout test is a combination of a client side
      helper/setup and server side actual tests.
      v2: Load weston-test.so, because create_client() needs it.
      v3: add a comment about IVI_TEST_SURFACE_ID_BASE.
      v4: Rebased to upstream weston-tests-env changes.
      Signed-off-by: Pekka Paalanen's avatarPekka Paalanen <pekka.paalanen@collabora.co.uk>
      Reviewed-by: Derek Foreman <derekf@osg.samsung.com> (v2)
    • Pekka Paalanen's avatar
      tests: add a basic ivi-shell test · 0eb09412
      Pekka Paalanen authored
      This simply tests that Weston starts with ivi-shell, and ivi_application
      is present.
      Changes in v3:
      - Rebased to upstream weston-tests-env changes.
      Signed-off-by: Pekka Paalanen's avatarPekka Paalanen <pekka.paalanen@collabora.co.uk>
      Reviewed-by: Derek Foreman <derekf@osg.samsung.com> (v2)
  7. 08 Apr, 2015 4 commits
  8. 07 Apr, 2015 7 commits
  9. 06 Apr, 2015 1 commit
  10. 02 Apr, 2015 4 commits
  11. 31 Mar, 2015 5 commits
  12. 30 Mar, 2015 4 commits
  13. 27 Mar, 2015 2 commits