explicitly define on a per testcase basis which extension needs to be loaded

Bug #634740 reported by Markus Korn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zeitgeist Framework
Fix Released
Undecided
Markus Korn

Bug Description

Right now we load all available extensions in our test runs. So if someone as a random (experimental) extension in ~/.local/share/zeitgeist/extensions which fails all our remote and engine testcases fail too.
As we have no influence on the installed extensions on the users system we should explicitly configure them on each test run.

Related branches

Revision history for this message
Markus Korn (thekorn) wrote :

In fact we should make sure that no non-core extension ever influence our testsuite, testing of 3rd party extensions should be done on their side.

Changed in zeitgeist:
assignee: nobody → Markus Korn (thekorn)
status: New → In Progress
Seif Lotfy (seif)
Changed in zeitgeist:
status: In Progress → Fix Released
status: Fix Released → Fix Committed
Changed in zeitgeist:
milestone: none → 0.6
Markus Korn (thekorn)
Changed in zeitgeist:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.