Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-dev] bug 309681 - coarsly analyze skipped WDF tests

It may be better to break the ticket into individual blocking bugs.  Keeping track in the bugdb usually provides for better history and easier maintenance than a Wiki page.

Goerler, Adrian wrote:
Hi Tom, Michael, others,
in the WDF test suite, we are still having a large number (~200) of test, which are skipped with @ToBeInvestigated. These are basically all tests, which would have failed upon the initial check in of the test suite. So far, we have not systematically analyzed these tests and know only very few details.
In order to get a better understanding of these skipped tests, we are currently doing a quick run over the issues to get a rough idea of their causes. Hopefully, this allows us to classify whether an issue is caused by
  • Different interpretation of the JPA spec
  • Exotic test model
  • Bug in EclipseLink
  • Bug in the test
  • Whatsoever
Coming to Ottawa in may, we’d like to take the chance to discuss selected issues with the team.
So far, I am keeping track of the results of the investigation in the bugzilla ticket 309681. I am not sure that this is a good idea as the ticket will get quite lengthy. Maybe a Wikipedia page would be better? Or an Excel? What do you think?
En passant, I have fixed some obvious issues with the test and the framework, which I would like to check in. Please find a patch in the bugzilla ticket.
Tested SE on MySQL and Oracle and EE on JBoss / MySQL.
Could you please have a look?
Adrian Görler

Pflichtangaben/Mandatory Disclosure Statements:

_______________________________________________ eclipselink-dev mailing list eclipselink-dev@xxxxxxxxxxx

Back to the top