1. 06 Jan, 2021 1 commit
  2. 05 Aug, 2020 1 commit
    • moto's avatar
      [CI] Run unit test with non-editable installation (#845) · 9ba02d5b
      moto authored
      We have been running unit test with editable installation. (i.e. `python setup.py develop`), with which we missed issues like #842. 
      
      This CC makes installation in CI non-editable, and change test directory structure so that the source code will not shadow the installed version of `torchaudio`. With simple `pytest test`, `pytest` modifies `sys.path` and prepend checked out repository, which shadows the installed version.
      
      To remedy this, the whole test suites has been moved from `./test` to `./test/torchaudio_unittest`. This adds nice module structure to our test code and we can do absolute import in each test module, which makes it possible again to run test with `python -m unittest torchaudio_unittest/XXX.py`
      
      This change does not affect the regular development process (`python setup.py develop` && `pytest test`)
      9ba02d5b
  3. 11 Jun, 2020 1 commit
    • moto's avatar
      Get rid of dynamic test suite generation (#716) · 08217121
      moto authored
      `type` used in `common_utils` generates test class definition in `common_utils` and
      this modifies the module state after it's imported. This is anti-pattern.
      This PR get rid of the related utility functions and define test suite manually.
      08217121