ant junitreport: Success rate 79.56%
by Darryl Miles
As part of release engineering, are the junit tests run in at least one configuration (JVM, Java version, JDBC driver, SQL server implementation) to prove they pass ? If so what configuration is used ?
Many of the tests fail for my configuration, Success rate 79.56%, is this to be expected ?
My configuration:
* Hibernate 3.2.0-ga
* JVM: Sun 1.5.0 x86_64/Linux
* JDBC Driver: mysql-connector-java-3.1.12-bin.jar
* SQL Server: MySQL 4.1.15
Out of the box, with Hypersonic SQL Success rate is 7.33%.
What is the purpose of the unit tests that are shipped with the product
and are the quality of those tests currently meeting the goals of that
purpose ?
I would like to think that if a unit test makes it into the distribution
to be shipped with the product that as a user I could gain some
confidence in knowing that the specific scenario that the unit test
embodies is verified as working against each subsequent release of the
product.
Darryl
19 years
Lucene: @Indexed -> @FullText
by Emmanuel Bernard
I want to rename @Indexed to @FullText to mark a class as "searchable"
The name is more appropriate to the context and less generic
@Entity
@FullText(index="commerce")
public class Order {
Anybody against or with a better name?
19 years
Revision 9989 of AbstractStatementExecutor and MySQL
by Donnchadh Ó Donnabháin
Hi everyone,
I've been looking at the most recent change to
AbstractStatementExecutor and it seems to assume that if a DDL
statement, in general, results in a commit that this will also happen
for a temporary table. In the case of MySQL, at least, this is not the
case. The code in AbstractStatementExecutor goes and creates the
temporary table in a new connection, which, in the case of MySQL, will
not be visible in the current transaction.
http://fisheye.jboss.com/browse/Hibernate/branches/Branch_3_2/Hibernate3/...
If this turns out to be a bug, I will create an isolated test case for
it and log a bug in JIRA.
Donnchadh
19 years
