Changes between Initial Version and Version 5 of Ticket #26677
- Timestamp:
- May 30, 2016, 5:31:34 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #26677
- Property Owner changed from to
- Property Status new → assigned
- Property Summary Run i18n tests on disposablle FS tree instead of source code → Run i18n tests on disposable FS tree instead of source code
- Property Component Testing framework → Internationalization
- Property Has patch set
- Property Triage Stage Unreviewed → Accepted
-
Ticket #26677 – Description
initial v5 1 Currently, tests that exercise translatable literal extraction to `.po` files by ''makemessages'' (located on `test_extraction.py`) and test that exercise compilation of `.po` files to `.mo` files by ''compilemessages'' (`test_compilation.py`) are run under the `test/i18n` test source code tree creating subdirectories and files under the different work projects/applications lo ated there.1 Currently, tests that exercise translatable literal extraction to `.po` files by ''makemessages'' (located on `test_extraction.py`) and test that exercise compilation of `.po` files to `.mo` files by ''compilemessages'' (`test_compilation.py`) are run under the `test/i18n` test source code tree creating subdirectories and files under the different work projects/applications located there. 2 2 3 3 Proposal is to copy the relevant filesystem tree to a tempdir as provided by `runtests.py` + `tempfile.mkdtemp()` as part of every test case setup. … … 6 6 7 7 * Avoid weird bogus errors and failures caused by stray directories left by previous runs/debugging sessions. 8 * Allows us to solve the fact that currently tests on `test_compilation.py` aren't marked as needing seralized execution and are actually being run in parallel which causes a couple of consecutive runs if the i18n test on my Ubuntu 1.4.04 system to report misleading failures, most probably because of race conditions.8 * Allows us to solve the fact that currently tests on `test_compilation.py` aren't marked as needing seralized execution and are actually being run in parallel. This, for instance, causes a couple of consecutive runs of the i18n test on my Ubuntu 1.4.04 system to report misleading failures, most probably because of race conditions. 9 9 * Ensure actual isolation among test cases 10 10 * Allow each of these test cases to be actually run in in parallel by our existing machinery. This allows us to be able to stop relying on `django.test.testcases.SerializeMixin`