We're updating the issue view to help you get more done. 

ConverterTest fails with SQL Server depending on collation

Description

In our case org.hibernate.test.converter.ConverterTest fails with SQL Server. I didn't dig how database is configured but it doesn't support character ț.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 org.junit.ComparisonFailure: expected:<Doroban[ț]ul> but was:<Doroban[?]ul> at org.junit.Assert.assertEquals(Assert.java:115) at org.junit.Assert.assertEquals(Assert.java:144) at org.hibernate.test.converter.ConverterTest.lambda$testJPQLUpperAttributeValueBindParameterType$2(ConverterTest.java:88) at org.hibernate.testing.transaction.TransactionUtil.doInJPA(TransactionUtil.java:205) at org.hibernate.testing.transaction.TransactionUtil.doInJPA(TransactionUtil.java:246) at org.hibernate.test.converter.ConverterTest.testJPQLUpperAttributeValueBindParameterType(ConverterTest.java:68) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.hibernate.testing.junit4.ExtendedFrameworkMethod.invokeExplosively(ExtendedFrameworkMethod.java:45) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.lang.Thread.run(Thread.java:748)

I don't think support of such charaters is goal of the test, so better to update it to work with more configurations.

Environment

None

Status

Assignee

Martin Šimka

Reporter

Martin Šimka

Fix versions

Labels

None

backPortable

Backport?

Suitable for new contributors

Yes, likely

Requires Release Note

None

backportDecision

None

Components

Affects versions

5.3.3

Priority

Major