1. 06 Jul, 2021 1 commit
  2. 18 Jun, 2021 1 commit
    • Jérome Perrin's avatar
      tests: also consider python unittest failures in functional tests · 1b1dbf60
      Jérome Perrin authored
      It can happen that a test running selenium fail in python, but not in selenium,
      like for example test_result_module/20210615-CDADEC14/183
      To prevent such tests from being reported as PASS, we make the total number of
      failures being the sum of the python unittest failures and the selenium failures.
  3. 17 Jun, 2021 1 commit
    • Kirill Smelkov's avatar
      tests: Teach test driver to pass testWendelinCore when run with wendelin.core 2 · 530e8b4e
      Kirill Smelkov authored
      This is follow-up to 5796a17a (core_test: Add test to make sure that
      wendelin.core basically works; !1429).
      In that commit it was said that testWendelinCore
          "currently passes with wendelin.core 1, which is the default.
           It also passes as live test with wendelin.core 2.
           However with wendelin.core 2 it currently fails when run on testnodes
           because we need to amend ERP5 test driver
           1. to run tests on a real storage instead of in-RAM Mapping Storage(*), and
           2. to spawn WCFS server for each such storage."
      This patch addresses that latter problem to run testWendelinCore under
      testnode infrastructure.
      @rafael and @jerome suggested that we can force a test to be run on a
      real storage via `runUnitTest --load --save` or via `--activity_node=n`.
      @rafael also suggested not to generally change the testing driver, but instead
      make step-by-step progress and first tag each test that uses wendelin.core with an
      option. Let's go this way now: runUnitTest/custom_zodb are taught to launch
      WCFS server if wendelin.core usage is requested and software is built with
      wendelin.core 2.
      With both changes combined testWendelinCore should now pass OK when run
      on a testnode with both wendelin.core 1 and wendelin.core 2.
      This patch is based on a draft patch by @rafael: rafael/erp5@14e3a777.
      This patch also relies on recent wendelin.core 2 wcfs.py rework which
      exposed functionality to start WCFS server and to further control it:
      /cc @tomo, @romain, @jerome, @seb
  4. 29 Apr, 2021 1 commit
  5. 23 Apr, 2021 1 commit
    • Arnaud Fontaine's avatar
      ERP5Workflow: DC Workflows are now ERP5 objects (!1378). · df85ef46
      Arnaud Fontaine authored
      This also moves all Configurator Workflows in workflow_module to portal_workflow
      (workflow_module was an implementation of Workflows based on ERP5 objects and
      not using DCWorkflow code).
      * Workflows are now defined on on portal_workflow._chains_by_type anymore but,
        as everything else, on the Portal Type itself.
      * portal_workflow can contain and work at the same time with legacy and new
        Workflows (ERP5Type/patches/DCWorkflow.py monkey-patching DCWorkflow classes
        to provide the same API).
      * Existing Workflow Scripts should work as they are and the code can be updated
        later on to take advantage of the new API:
        + With legacy implementation Workflow {Scripts,Transitions,Worklists,States}
          were in a Folder ({scripts,transitions,worklists,states} attribute) but
          all of these are now in the Workflow itself and their IDs are prefixed
          (PropertySheet-style), for example `script_`. Legacy attributes are
          provided in new implementation to call the new API.
        + When calling a Workflow Script, `container` was bound to its parent, namely
          WF.scripts (Folder) and a Workflow Script could call another. Now `container`
          is bound to the WF itself and Workflow Scripts are in a Workflow directly.
          New implementation `scripts` attribute handle such use case.
        + Override portal_workflow.__getattr__ so that a Workflow Script can call
          another one without prefix.
      * Worklist are Predicate: Worklist filter objects based on given criterions and
        thus it makes more sense for a Worklist to be a Predicate (albeit a Predicate
        with only Identity Criterion and nothing else).
        + Criterion Properties:
          * state_variable.
          * local_roles (SECURITY_PARAMETER_ID).
          * Any Workflow Variables with for_catalog == 1.
      erp5_performance_test:testWorkflowPerformance were ran to compare DCWorkflow
      and ERP5Workflow implementations and it seems to be about 4% slower with the
      new implementation (legacy: 7.547, 7.593, 7.618, 7.59, 7.514 and new: 7.842,
      7.723, 7.902, 7.837, 7.875).
      Work done by Wenjie Zheng, Isabelle Vallet, Sebastien Robin and myself.
  6. 07 Sep, 2020 2 commits
  7. 03 Aug, 2020 1 commit
  8. 02 Jul, 2020 4 commits
  9. 15 May, 2020 1 commit
    • Jérome Perrin's avatar
      ERP5TypeTestSuite: let testsuite decide the log directory · d16b9ff9
      Jérome Perrin authored
      Using the test class name was causing conflicts on some test classes.
      CodingStyleTest was a case, all test use CodingStyleTest class with an
      environment variable to control which business template is tested. In
      this case, we want one log directory for each business template.
      Introduce a getLogDirectoryPath method that's supposed to create and
      return the path of the directory to use for log and override this method
      for the special case of coding style test.
  10. 12 May, 2020 1 commit
  11. 03 Apr, 2020 1 commit
  12. 02 Apr, 2020 1 commit
  13. 27 Mar, 2020 1 commit
  14. 09 Mar, 2020 1 commit
  15. 03 Dec, 2019 1 commit
  16. 06 Nov, 2019 1 commit
  17. 31 Oct, 2019 1 commit
    • Arnaud Fontaine's avatar
      ZODB Components: Migrate Products.ERP5VCS (MR !973). · 2cff7d32
      Arnaud Fontaine authored
      Moved 'git_askpass' shell script to product/ERP5/bin (considering that this
      is a very short shell script which hasn't changed in 7 years, no need to move
      it to the ZODB which would require creating a temporary file...).
      After updating erp5_forge, you should delete 'product/ERP5VCS/' directory
      as this will only contain '.pyc' files.
      /reviewed-on !973
  18. 30 Sep, 2019 1 commit
  19. 20 Sep, 2019 1 commit
  20. 10 Dec, 2018 1 commit
  21. 11 Oct, 2018 1 commit
  22. 09 Jan, 2018 1 commit
  23. 08 Jan, 2018 1 commit
  24. 07 Mar, 2017 1 commit
  25. 23 Oct, 2015 1 commit
  26. 05 Oct, 2015 1 commit
  27. 12 Jan, 2015 1 commit
  28. 10 Jan, 2014 1 commit
  29. 25 Sep, 2013 2 commits
  30. 10 Sep, 2013 2 commits
    • Arnaud Fontaine's avatar
      ZODB Components: Revert 'Allow to execute runUnitTest for bt5 Test Components'... · c35d24e8
      Arnaud Fontaine authored
      ZODB Components: Revert 'Allow to execute runUnitTest for bt5 Test Components' (a771dca4) to fix tests bootstrap.
      The new syntax to load ZODB Tests Components is:
      runUnitTest BT_TITLE:TEST_NAME
      That commit was too adhoc as it was relying upon filesystem to load Tests
      Components and was not behaving like any other Components (versions was not
      available and other Components were not importable).
      At the end, it would have meant that a Test Component ran through runUnitTest
      and Live Tests (in ERP5 itself) would have behaved differently, thus instead:
      1/ Install BT_TITLE dependencies and its test dependencies (new bt property to
         specify bt to be installed only for tests on a fresh instance).
      2/ The site is loaded.
      3/ Load the test by importing it like any other Components.
    • Arnaud Fontaine's avatar
      ZODB Components: Allow to execute runUnitTest for bt5 Test Components. · a771dca4
      Arnaud Fontaine authored
      Usage: runUnitTest test.VERSION.REFERENCE as exported on the filesystem. Also,
      add bt5 Test Components to tests being run through erp5testnode.
  31. 27 Feb, 2013 1 commit
  32. 21 Feb, 2013 2 commits
  33. 31 Jan, 2013 1 commit