WIP: software/erp5/tests: Extend WCFS test scope
This patch enhances the ERP5 + WCFS integration tests. Before it was only minimal; now it runs actual workload of writing and reading ZBigArray to the ZODB. This is necessary to securely verify WC2 is working with ERP5.
For testing WCFS against NEO, we need compatible NEO => WCFS and ZODB => WCFS versions for successful tests. This is the reason why we need to add a specific 'test.cfg' here, which ensures compatible versions are installed.
We had to implement the new tests in a separate test environment, because SlapOS Integration tests run with python3, but we need python2 for NEO support. We need NEO, because we want to test if WCFS works with NEO client.
This is a follow-up MR for !1283 (closed).
This MR is not supposed to be merged very soon. Its purpose is to keep track of some work which is already done, or - in the words of Kirills original suggestion:
For
extend WCFS testswe can keep it in a MR and in a slapos branch where NEO is switched to interoperable version, and probably setup additional testsuite where that functionality will be tested as well. This way it won't be lost and will be kept ready to be merged once if/when hopefully NEO/py - NEO/go interoperability issues would be resolved.
There are various details in the given patch which already received some feedback about how it should be adjusted.
We should amend the patch so that extended wcfs tests doesn't require a test.cfg:
For (a) Subtest (py2 NEO), I don't know all this well, but we could also write run a python script from ERP5 (like we do with the
_addPythonScriptmethod) or by putting the code in portal_components if it needs unrestricted access. We could also maybe have a business template in erp5.git containing the test code if that makes sense. Another way might be to use the python interpreter with all packages installed that isbin/pythonin the software folder to execute the python code.
(see !1283 (comment 174177) for Jéromes original comment)