explicitly define on a per testcase basis which extension needs to be loaded
Bug #634740 reported by
Markus Korn
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/
As we have no influence on the installed extensions on the users system we should explicitly configure them on each test run.
Related branches
lp:~thekorn/zeitgeist/fix-634740-634744-testrunner-improvements
- Siegfried Gevatter: Approve
- Seif Lotfy: Needs Fixing
-
Diff: 607 lines (+293/-76)9 files modifiedbug_testrunner.py (+10/-0)
test/blacklist-test.py (+3/-1)
test/engine-extension-test.py (+26/-18)
test/engine-test.py (+6/-4)
test/loggers-datasources-recent-test.py (+16/-4)
test/remote-test.py (+36/-9)
test/run-all-tests.py (+98/-27)
test/sql-test.py (+7/-1)
test/testutils.py (+91/-12)
Changed in zeitgeist: | |
status: | In Progress → Fix Released |
status: | Fix Released → Fix Committed |
Changed in zeitgeist: | |
milestone: | none → 0.6 |
Changed in zeitgeist: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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.