otoniel-isidoro / dbassert Goto Github PK

What steps will reproduce the problem?

1. Create a simple Java program to load some fixtures
2. Run it
3. For just 50 rows, it takes more than 1 minute.

What is the expected output? What do you see instead?

Hey, need to be very faster than this. :-)
Check the output for 50 rows:
---------------------------------------------
loading fixtures Tue Jun 15 12:27:54 BRT 2010
fixtures loaded Tue Jun 15 12:29:16 BRT 2010
---------------------------------------------

What version of the product are you using? On what operating system?

Sun Java 1.6.0_20, dbAssert 0.9.2 on GNU/Linux Ubuntu 10.04

Please provide any additional information below.

I thought there were some problems with JUnit integration, then I wrote another 
file with just dbAssert stuff, but it is still slow. :-(
I also use pure Jyaml to load the fixture data, and it just took 1 second.

.

What steps will reproduce the problem?
1. Create DbAssert object in a class in a completely separate package
2. Try to call dbAssert.table("table").<anything>

What is the expected output? What do you see instead?
Expected OK. Get compile error "The type Condition is not visible"

What version of the product are you using? On what operating system?
9.1, Java 1.5, OS X 10.5

Please provide any additional information below.
I'm assuming I'm supposed to use the net.codemate packages to follow the
api in the examples.

I have a table called "domain" in which a field "parentId" has foreign key 
constraint which references primary key "domainId" of the same table. My 
domain.yml file looks like this:
----------------------------------------------------
domain4:
    domainid: 4
    name: domain4.com
domain5:
    domainid: 5
    name: domain5.domain4.com
    parentId: 4
domain6:
    domainid: 6
    name: domain6.domain5.domain4.com
    parentId: 5
domain7:
    domainid: 7
    name: domain7.domain5.domain4.com
    parentId: 5
domain8:
    domainid: 8
    name: domain8.domain4.com
    parentId: 5
----------------------------------------------------

When I load this fixture using dbSource.fixture("domain") foreign key 
constraint violation occurs and the fixture is not loaded.

On debugging the source for dbassert, I found that records in yml file are read 
into a Map using Yaml.load method. This map is a HashMap and the keySet() of 
this map does not returns records in the order in which they exist in yml file. 
For example, in my case the order was {domain6, domain7, domain4, domain5, 
domain8}.

Is there any workaround for this?

I found that DB2 doesn't seem to like the rs.isLast() method. The revised code 
I provided gets you the same functionality but without the method call, it 
could potentially protect against other picky DBs.

Can you provide a maven repository for dbassert? If your interested I'm
willing to submit a patch with a POM and ant tasks. 

What steps will reproduce the problem?

1. Use getClass() on source(<name>,<class>)
2. Try to load a fixture from a class outside a package 

What is the expected output? What do you see instead?

Load fixture. But I get a java.lang.StringIndexOutOfBoundsException: String
index out of range: -1.

What version of the product are you using? On what operating system?

0.9.2 on GNU/Linux.

Please provide any additional information below.

Ok, better run with a package as a namespace limiter, but for some tests
maybe it's a good idea deal with the absence of a dot on the class name, like:

if(clazzName.lastIndexOf(".")>0)
   clazzName = clazzName.substring(0,
clazzName.lastIndexOf(".")).replace(".", "/");
fixturePath = clazzName + "/fixtures/" + fixName + ".yml";

Thanks.

In order to be able to pass in different database names from different unit 
tests need to add the ability for DbAssert.init to take the driver class, url, 
user name and password as parameters instead of a yml file.