An error occurred fetching the project authors.
  1. 02 Mar, 2020 1 commit
  2. 22 Jan, 2020 1 commit
  3. 28 Nov, 2019 1 commit
    • Jérome Perrin's avatar
      testXHTML: test portal types also from tools · 56e16adc
      Jérome Perrin authored
      Some portal types such as Business Template were not tested by testXHTML
      because this tests started by modules and recursively tests views based
      on allowed content types. Because of this approach, types that are not
      created in a module but in a tool were never tested.
      
      With unittest, the only way to dynamically add test methods to a class
      is to generate a test class in test_suite function. At this stage, the
      ERP5 site is not created yet, so the test had to introspects business
      templates XML.
      
      This now uses a slightly different approach, instead of finding modules
      and chain of allowed content types from business template XML, we only
      use business template to introspect the list of actions.
      The lookup of the appropriate containers is no longer done before setup
      by static analysis of business templates XML, but later once the site is
      created, by dynamic analysis of the modules and allowed content types on
      the running ERP5 site during the test method.
      If we don't find a chain of portal types, we create the test document in
      portal_trash, a tool without filter of content types.
      
      This way, we can test all views of all portal types. This revealed a few
      problems:
       - we need developer role to create components in portal_components, for
      this we add developer role to the current user.
       - Delivery Cell portal type looks not used, there are no container
      accepting it. We don't test delivery cell views for this reason.
       - VCS view on business template needs preferences and working copy
      setup. We just mark this test as expected failure for now.
       - Solver Decision has a form conditionnaly displayed when there's a
      relation to a solver, but this test does not evaluate action conditions
      and does not allow to call a script (that would made it possible to
      modify the document so that the condition is true). For now we also
      mark this as expected failure.
      56e16adc
  4. 25 Oct, 2019 1 commit
  5. 04 Sep, 2019 1 commit
  6. 10 Jul, 2019 1 commit
    • Arnaud Fontaine's avatar
      erp5_ace_editor: Removed. · 94a179a6
      Arnaud Fontaine authored
      * Not updated for many years (CodeMirror has since replaced it).
      * There are now 2 other better source code editors (CodeMirror and Monaco).
      94a179a6
  7. 02 Jan, 2019 1 commit
  8. 24 Oct, 2018 1 commit
  9. 01 Oct, 2018 2 commits
  10. 31 Jul, 2018 1 commit
  11. 05 Jul, 2018 1 commit
    • Ayush Tiwari's avatar
      [erp5_core]: Use Diff Tool to Beautify History Tab for ERP5 objects · 2f121c19
      Ayush Tiwari authored
      The Diff view in new UI will be using IFrames to display the diff.
      
      Also, add changes in tests:
      
      erp5_ui_test: Update history test according to use of diff gadget
      erp5_web_renderjs_ui_test: Update tests according to new Diff view for Historical Revisions
      testXHTML: Add Historical Comparison View to the list of listbox with no selection name
      testXHTML: Simplify test_html_file and include way to ignore single html file
      2f121c19
  12. 08 Jun, 2018 3 commits
  13. 15 Apr, 2018 1 commit
  14. 30 Mar, 2018 3 commits
  15. 26 Oct, 2017 1 commit
  16. 25 Oct, 2017 2 commits
  17. 17 Oct, 2017 3 commits
  18. 20 Sep, 2017 1 commit
  19. 23 Dec, 2016 1 commit
  20. 21 Sep, 2016 1 commit
  21. 19 May, 2016 2 commits
  22. 27 Apr, 2016 1 commit
  23. 29 Jan, 2016 1 commit
  24. 21 Jan, 2016 1 commit
  25. 18 Dec, 2015 1 commit
  26. 28 Jul, 2015 1 commit
  27. 23 Mar, 2015 1 commit
  28. 12 Jan, 2015 2 commits
  29. 16 Dec, 2014 1 commit
  30. 12 Dec, 2014 1 commit