[tracker] functional-tests: Start/stop processes in correct order, miner after extract

[Martyn James Russell <mr src gnome org>]

commit a29bff17bbea0003529eeb80fd51b7f339075f0c
Author: Martin Kampas <martin kampas+gnomebugs ubedi net>
Date:   Mon Feb 24 16:10:17 2014 +0000

    functional-tests: Start/stop processes in correct order, miner after extract
    
    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.

 .../functional-tests/301-miner-resource-removal.py |    7 ++++---
 1 files changed, 4 insertions(+), 3 deletions(-)
---
diff --git a/tests/functional-tests/301-miner-resource-removal.py 
b/tests/functional-tests/301-miner-resource-removal.py
index 506e8d4..cf0af78 100755
--- a/tests/functional-tests/301-miner-resource-removal.py
+++ b/tests/functional-tests/301-miner-resource-removal.py
@@ -69,8 +69,6 @@ class MinerResourceRemovalTest (ut.TestCase):
         self.system.set_up_environment (CONF_OPTIONS, None)
         self.store = StoreHelper ()
         self.store.start ()
-        self.miner_fs = MinerFsHelper ()
-        self.miner_fs.start ()
 
         # GraphUpdated seems to not be emitted if the extractor isn't running
         # even though the file resource still gets inserted - maybe because
@@ -78,11 +76,14 @@ class MinerResourceRemovalTest (ut.TestCase):
         self.extractor = ExtractorHelper ()
         self.extractor.start ()
 
+        self.miner_fs = MinerFsHelper ()
+        self.miner_fs.start ()
+
     @classmethod
     def tearDownClass (self):
         self.store.bus._clean_up_signal_match (self.graph_updated_handler_id)
-        self.extractor.stop ()
         self.miner_fs.stop ()
+        self.extractor.stop ()
         self.store.stop ()
 
     def setUp (self):