failing Enum unit tests

Bug #1038910 reported by Ralf Claussnitzer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Goobi.Production
Status tracked in 1.10
1.10
New
Undecided
Unassigned
1.8
Fix Released
Low
Henning Gerhardt

Bug Description

Undetected regression. Some Enum unit tests fail since refactoring of translation mechanism:

[junit] Running org.goobi.production.flow.statistics.enums.CalculationUnitTest
[junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 0.191 sec
[junit] Test org.goobi.production.flow.statistics.enums.CalculationUnitTest FAILED
[junit] Running org.goobi.production.flow.statistics.enums.ResultOutputTest
[junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 0.144 sec
[junit] Test org.goobi.production.flow.statistics.enums.ResultOutputTest FAILED
[junit] Running org.goobi.production.flow.statistics.enums.StatisticsModeTest
[junit] Tests run: 4, Failures: 0, Errors: 1, Time elapsed: 0.154 sec
[junit] Test org.goobi.production.flow.statistics.enums.StatisticsModeTest FAILED
[junit] Running org.goobi.production.flow.statistics.enums.TimeUnitTest
[junit] Tests run: 5, Failures: 0, Errors: 1, Time elapsed: 0.142 sec
[junit] Test org.goobi.production.flow.statistics.enums.TimeUnitTest FAILED

Root cause is the use of static initializers in Message bundle class relying on existent FacesContext.

Related branches

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.