Ticket #4324 (closed: wontfix)
TestViewer: support python unit tests
| Reported by: | Janik Zikovsky | Owned by: | Janik Zikovsky |
|---|---|---|---|
| Priority: | minor | Milestone: | Release 2.1 |
| Component: | Infrastructure | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Tester: | Andrei Savici |
Description
Change History
comment:2 Changed 9 years ago by Janik Zikovsky
Refs #4324: Fix PyUnitTests' test names so that...
... they do not have the module name twice. Also fixed the TestViewer so that it can run python unit tests
Changeset: 9196e3d882cfcf05c45621729f77a2b665a7d402
comment:4 Changed 9 years ago by Janik Zikovsky
Refs #4324: Better python unit test fail reports
Changeset: e3d24e956a12e9369e3b710df0b1b234b4e96e40
comment:5 Changed 9 years ago by Janik Zikovsky
Refs #4324: Better python unit test fail reports
Changeset: 51528ba42af7cce55a4923f02e9be79f0e16aea2
comment:6 Changed 9 years ago by Janik Zikovsky
- Status changed from accepted to verify
- Resolution set to fixed
comment:8 Changed 9 years ago by Janik Zikovsky
Refs #4324: Fix PyUnitTests' test names so that...
... they do not have the module name twice. Also fixed the TestViewer so that it can run python unit tests
Changeset: 9196e3d882cfcf05c45621729f77a2b665a7d402
comment:9 Changed 9 years ago by Janik Zikovsky
Refs #4324: Better python unit test fail reports
Changeset: e3d24e956a12e9369e3b710df0b1b234b4e96e40
comment:10 Changed 9 years ago by Janik Zikovsky
Refs #4324: Better python unit test fail reports
Changeset: 51528ba42af7cce55a4923f02e9be79f0e16aea2
comment:11 Changed 9 years ago by Michael Reuter
- Status changed from verify to verifying
- Tester set to Michael Reuter
comment:12 Changed 9 years ago by Michael Reuter
- Status changed from verifying to reopened
- Resolution fixed deleted
I believe VanillaPythonTest and PythonReductionTest are Python unit tests and the TestViewer refuses to run them. All of the VanillaPythonInterfaceTest:InstrumentTests and VanillaPythonInterfaceTest:BoundedValidatorTests fail, but they work just fine via ctest. They complain like:
Traceback (most recent call last):
File "/home/2zr/build/Mantid-release/bin/VanillaPythonInterfaceTest.py", line 184, in
unittest.main(testRunner=xmlrunner.XMLTestRunner(output='Testing'))
File "/usr/lib64/python2.6/unittest.py", line 815, in __init__
self.parseArgs(argv)
File "/usr/lib64/python2.6/unittest.py", line 842, in parseArgs
self.createTests()
File "/usr/lib64/python2.6/unittest.py", line 848, in createTests
self.module)
File "/usr/lib64/python2.6/unittest.py", line 612, in loadTestsFromNames
suites = [self.loadTestsFromName(name, module) for name in names]
File "/usr/lib64/python2.6/unittest.py", line 604, in loadTestsFromName
(obj, test))
TypeError: calling returned , not a test
Also, it's about 4 times slower (with In Parallel on) to run than straight ctest (with -j8).
Certain performance tests complain that they fail when they shouldn't have run at all
- MDEventsTest:IntegratePeaksMDTestPerformance
- DataHandlingTest:LoadInstrumentTestPerformance
- AlgorithmTest:GetDetOffsetsMultiPeaksTestPerformance
- AlgorithmTest:DiffractionFocussing2TestPerformance
comment:14 Changed 9 years ago by Janik Zikovsky
- Milestone changed from Iteration 32 to Iteration 33
comment:18 Changed 9 years ago by Janik Zikovsky
- Status changed from accepted to verify
- Resolution set to wontfix
I decided to remove support for Python unit tests instead. It was too slow.
comment:19 Changed 8 years ago by Andrei Savici
- Status changed from verify to verifying
- Tester changed from Michael Reuter to Andrei Savici
comment:21 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 5171
Refs #4324. Adding stub for new implicit function.