1. 11 Oct, 2021 1 commit
  2. 08 Oct, 2021 2 commits
  3. 10 Aug, 2021 1 commit
  4. 02 Jul, 2021 1 commit
    • Xavier Thompson's avatar
      slapos-sr-testing: Add instance parameters to filter what is tested · c2856de1
      Xavier Thompson authored
      The two following instance parameters now exist:
      - `only-sr`: a list of software releases names to test
      - `unittest-args`: a list of arguments for unittest
      
      By default:
      - all software releases are tested
      - the unittest arguments are ["discover", "-v"]
      
      Single values are accepted even if they are not in a list.
      c2856de1
  5. 23 Mar, 2021 1 commit
  6. 21 Mar, 2021 1 commit
    • Julien Muchembled's avatar
      slapos-sr-testing: do not end paths with / · 0803b816
      Julien Muchembled authored
      This may lead to weird like ...//... or worse: here, the [gcc] part of
      the tested SR will do "os.path.dirname('/usr/bin/')" (when using system
      gcc), causing ${gcc:prefix} to be invalid ('/usr/bin' instead of '/usr')
      and most sharable parts will rebuild (different [gcc] signature).
      0803b816
  7. 27 Nov, 2020 1 commit
    • Jérome Perrin's avatar
      software/slapos-sr-testing: use nxdtest · 3a1e5628
      Jérome Perrin authored
      Change to run all tests with python -m unittest, which will allow us to
      remove workaround for the $PYTHONPATH set by setup.py test.
      
      For this we use `[python-interpreter]` which uses pygolang.main to behave
      like a "normal" python interpreter with eggs available, but without the
      usual problems of interpreters generated by zc.recipe.eggs - it supports
      all command line flags and have current directory in sys.path.
      
      Tests now have an explicit name, that we set to the software name as before,
      and the special test dynamically checking all profiles json schemas (part
      of slapos.cookbook egg, at the root of slapos repository),is named
      json-schemas. It is also changed to run as default tests in python2 and
      python3, not only in extras for python2.
      3a1e5628
  8. 28 Sep, 2020 1 commit
  9. 21 Aug, 2020 1 commit
  10. 05 Aug, 2020 1 commit
    • Jérome Perrin's avatar
      software/slapos-sr-testing: generate an environment script · dbf762f1
      Jérome Perrin authored
      Using an script to set the environment is easier to use, but the main
      reason is that if we want to be able to use shared part from outer
      slapos (like when using in theia or slaprunner), the working directory
      for test must be contained in the instance directory of the outer
      slapos, so that when we run slapos node prune in the outer slapos this
      command can see that shared parts are used.
      dbf762f1
  11. 22 Jun, 2020 1 commit
  12. 10 Mar, 2020 1 commit
  13. 05 Mar, 2020 1 commit
  14. 03 Feb, 2020 1 commit
  15. 05 Dec, 2019 1 commit
  16. 30 Aug, 2019 1 commit
  17. 28 Aug, 2019 1 commit
  18. 26 Jul, 2019 1 commit
  19. 25 May, 2019 1 commit
  20. 09 Mar, 2019 1 commit
  21. 07 Feb, 2019 1 commit
  22. 22 Jan, 2019 1 commit
  23. 20 Dec, 2018 1 commit
    • Łukasz Nowak's avatar
      slapos-sr-testing: Common testing for Software Releases · 9fae7463
      Łukasz Nowak authored
      Since some software releases have unit tests, it is good idea to run the
      tests for each commit on slapos branch.
      
      This SR follow slapos-testing SR in a way how tests are grouped and run.
      
      Fixed erp5.util is used to expose good test suite names.
      9fae7463
  24. 12 Dec, 2018 1 commit
  25. 05 Dec, 2018 1 commit
  26. 27 Nov, 2018 1 commit
  27. 23 Nov, 2018 2 commits
  28. 02 Sep, 2018 1 commit
  29. 28 Jun, 2018 1 commit
  30. 22 Jun, 2018 1 commit
  31. 04 Apr, 2018 1 commit
    • Jérome Perrin's avatar
      slapos-testing: rework to use buildout to install eggs and dependencies · c91c4722
      Jérome Perrin authored
      Instead of letting `python setup.py test` install the depencies, use
      buildout way of installing the eggs.
      
      This software use `interpreter` recipe of `zc.recipe.egg` to install a
      python with all eggs pre-installed. This is a way to get all the
      dependencies at install time instead of getting them at run time from
      pypi when running `python setup.py test`.
      `erp5.util.testsuite` has been extended to support a parameter to
      specify which python interpreter to use.
      
      One issue is that this way of installing eggs by buildout cause chicken
      and egg problem: cloning repository containing `slapos.recipe.cmmi`
      needs git, and to compiling git needs `slapos.recipe.cmmi`.
      The consequence of this is that re-running software will install too
      many parts again.
      One solution for this would be to clone `slapos.recipe.cmmi` with a
      `git` command provided by testnode or system package.
      Another solution would be to not install `slapos.recipe.cmmi` develop
      egg, simply install the egg from it's current pypi version while
      installing the software (running tests will be from the git checkout
      anyway).
      For now this is open issue.
      
      Another point of attention is that `python setup.py test` install the
      requirements listed in `test_requires`, but `zc.recipe.egg` does not
      provide a way of installing these. Some of our packages have `[test]`
      entrypoints, in this case, the software installs the test entrypoints.
      For others, we install the eggs.
      
      Other improvements:
       * use a simple `slapos.recipe:wrapper` instead of `slapos.cookbook:egg_test`
       * fix the typo in repository name erp5-util-repository ->
         erp5.util-repository ( this mean we will have to fix the test suites in
         nexedi ERP5 )
       * document "what is this software" and a scenario of how this software
         can be used to develop slapos eggs.
       * switch to buildout-hash.cfg for easier template hash management.
      c91c4722
  32. 28 Mar, 2018 1 commit
  33. 27 Mar, 2018 1 commit
    • Alain Takoudjou's avatar
      monitor: move scripts wrapper and logrotate conf to buildout, uses some new... · 47644132
      Alain Takoudjou authored
      monitor: move scripts wrapper and logrotate conf to buildout, uses some new promises from slapos.toolbox
      
      monitor was updated in slapos.toolbox to not generate promise launcher scripts anymore. All
      generated scripts are now in buildout.
      Monitor promise run script is removed from cron, slapgrid is used to run promises.
      Replace some old promises by the new ones from slapos.toolbox. Cleanup monitor configuration.
      Monitor report and monitor-promises directory are now obsolete.
      47644132
  34. 16 Mar, 2018 1 commit
  35. 12 Feb, 2018 1 commit
  36. 01 Feb, 2018 1 commit
  37. 31 Jan, 2018 2 commits