Bug 43454 - Test fails on 4.2-0 for 85_ucs-translation-template/01_merge_new_module
Test fails on 4.2-0 for 85_ucs-translation-template/01_merge_new_module
Status: REOPENED
Product: UCS Test
Classification: Unclassified
Component: General
unspecified
Other Linux
: P5 normal (vote)
: ---
Assigned To: Eduard Mai
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-01-31 12:26 CET by Alexander Kläser
Modified: 2019-09-20 15:21 CEST (History)
3 users (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:
best: Patch_Available+


Attachments
Adjustments to apply tests on 4.2-0 code (2.42 KB, patch)
2017-01-31 12:29 CET, Alexander Kläser
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kläser univentionstaff 2017-01-31 12:26:59 CET
I adjusted the SVN URL to 4.2-0 and observed that the 85_ucs-translation-template/01_merge_new_module test fails.
Comment 1 Alexander Kläser univentionstaff 2017-01-31 12:28:07 CET
Eduard, could you have a look at this?
Comment 2 Alexander Kläser univentionstaff 2017-01-31 12:29:19 CET
Created attachment 8387 [details]
Adjustments to apply tests on 4.2-0 code

Here are the changes that I applied to both i18n tests.
Comment 3 Stefan Gohmann univentionstaff 2017-03-20 08:46:53 CET
For me, it is not release critical. So, my suggestion disable the test case and move it to 4.2-0-errata.
Comment 5 Stefan Gohmann univentionstaff 2017-03-22 10:40:52 CET
OK, leaving as open and move to 4.2-0-errata.
Comment 6 Eduard Mai univentionstaff 2017-03-22 11:00:18 CET
Thoughts on this: both tests 00 and 01 in 85_ucs-translation-template test suite are flawed in that they checkout the public Univention SVN repository during runtime. This will (theoretically) broaden the test surface. The downside is, that it will not play well in some of our existing testing environments and adds additional maintenance overhead when those change. Additionally its not necessary for the goal: test the univention-ucs-translation-* tools and the translationhelper module. For this, static testing data is sufficient.
Comment 7 Philipp Hahn univentionstaff 2019-09-20 15:21:21 CEST
The test still references SVN: <http://forge.univention.org/svn/dev/branches/ucs-4.1/ucs-4.1-1/management>
We switched to GIT: <https://github.com/univention/univention-corporate-server>