1. 18 Mar, 2019 1 commit
  2. 05 Mar, 2019 1 commit
  3. 11 Feb, 2019 1 commit
  4. 05 Jan, 2019 1 commit
  5. 21 Jul, 2018 1 commit
    • Sam Thursfield's avatar
      functional-tests: Fix more issues in awaiting for property changes · df0fa863
      Sam Thursfield authored
      We actually get a GraphUpdated signal per RDF class, and we need to
      filter out those we don't care about.
      
      This was breaking tests in some cases as they would get double
      notifications and get ahead of themselves. For example the
      410-extractor-decorator test would wait for changes to nie:title on
      an nmm:MusicPiece resource. But music files also have class nfo:Audio
      and so there would be two GraphUpdated signals for each change, one
      for the nmm:MusicPiece class and one for the nfo:Audio class.
      df0fa863
  6. 19 Jul, 2018 1 commit
  7. 11 Aug, 2015 1 commit
  8. 26 Dec, 2014 2 commits
  9. 31 Jul, 2014 2 commits
    • Sam Thursfield's avatar
      functional-tests: Rewrite DConf code to use GObject introspection · bda89012
      Sam Thursfield authored
      The tests will now detect if the DConf backend is not in use and raise
      an error, where previously tests would fail for confusing reasons. Also,
      we no longer have to shell out to 'gsettings' to set up the
      configuration.
      
      Configuration values now have to be specified as GLib.Variant instances
      instead of Python types. That's a bit of a pain. PyGI should have a way
      of creating a GVariant from an arbitrary Python value, but I didn't find
      one.
      bda89012
    • Sam Thursfield's avatar
      functional-tests: Replace use of PyGObject and PyGTK with PyGI · e9b3bb58
      Sam Thursfield authored
      If we do 'import gobject' anywhere then we cannot use the new
      GObject-introspection based Python bindings, because they conflict.
      
      This change means the functional tests can now use PyGI, instead of the
      deprecated and out-of-date PyGObject and PyGTK.
      
      Note that the dbus-python bindings are still widely used in the
      functional-tests. These work fine but are deprecated. We should
      switch to using GDBus through GObject-introspection instead when possible.
      e9b3bb58
  10. 24 Feb, 2014 2 commits
    • Martin Kampas's avatar
      functional-tests: Don't require miner-fs being idle for testing data inserted · 98781aa0
      Martin Kampas authored
      In many test cases the tracker_miner_fs_wait_for_idle() call is used to detect
      miner operation has completed. It returns when miner's status changes to
      "Idle" (or on timeout). Unfortunately at the time miner goes idle it is not
      guaranteed the data are already in store - and the related test fails.
      
      The test case 301-miner-resource-removal.py does it a better way - it listens
      to GraphUpdated signal sent by store and waits until the desired resource is
      announced being added or removed.
      
      There is comment inside 301-miner-resource-removal.py: "FIXME: put this stuff
      in StoreHelper". This patch is to follow that comment.
      
      Needed by tracker-tests-310-fts-indexing-use-graph-updated-signal.patch.
      98781aa0
    • Martin Kampas's avatar
      functional-tests: Start/stop processes in correct order, miner after extract · a29bff17
      Martin Kampas authored
      The process tracker-miner-fs causes the process tracker-store be started
      automatically via the D-Bus service autostart mechanism. As the test case
      needs to start and control the processes itself, it is necessary to start them
      in order of their dependencies, so the D-Bus autostart does not happen.
      a29bff17
  11. 29 Sep, 2011 1 commit