junit.framework.AssertionFailedError

unsupportedList expected:<0> but was:<8> at org.apache.derbyTesting.functionTests.tests.jdbc4.UnsupportedVetter.testSupportedMethods(UnsupportedVetter.java:381) at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:120) at org.apache.derbyTesting.junit.BaseJDBCTestCase.runBareOverridable(BaseJDBCTestCase.java:443) at org.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:460)

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web1719

  • via db-derby-dev by Rick Hillegas, 9 months ago
    unsupportedList expected:<0> but was:<8> at org.apache.derbyTesting.functionTests.tests.jdbc4.UnsupportedVetter.testSupportedMethods(UnsupportedVetter.java:381) at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java
  • via sourceforge.net by Unknown author, 1 year ago
    expected:<1> but was:<0> at junit.framework.Assert.assertEquals...
  • via sourceforge.net by Unknown author, 1 year ago
    expected:<1> but was:<0> at junit.framework.Assert.assertEquals...
  • Stack trace

    • junit.framework.AssertionFailedError: unsupportedList expected:<0> but was:<8> at org.apache.derbyTesting.functionTests.tests.jdbc4.UnsupportedVetter.testSupportedMethods(UnsupportedVetter.java:381) at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:120) at org.apache.derbyTesting.junit.BaseJDBCTestCase.runBareOverridable(BaseJDBCTestCase.java:443) at org.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:460) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.