It feels like we need an integration test to start/stop a MongoDB
instance... same for the other guy.
Gary
On Wed, Sep 24, 2014 at 9:59 PM, Matt Sicker wrote:
> There's several tests for any NoSQL implementation following the general
> contract of how they're all supposed to work. The MongoDB d
There's several tests for any NoSQL implementation following the general
contract of how they're all supposed to work. The MongoDB driver should be
safe to update, but the Lightcouch one is still rather new, so I wouldn't
trust a new version without perusing their changelog.
On 24 September 2014 2
Matt,
This could wait for 2.2 unless you have time to test. Right now, it seems
there is no way to test this from the build.
Gary
On Sun, Sep 14, 2014 at 12:51 AM, Gary Gregory
wrote:
> If you have time to check this for 2.1 that would be nice.
>
> Gary
>
> On Thu, Sep 11, 2014 at 3:03 PM, Mat
If you have time to check this for 2.1 that would be nice.
Gary
On Thu, Sep 11, 2014 at 3:03 PM, Matt Sicker wrote:
> Whoops, sort of forgot. It would be safe to upgrade EclipseLink. I'm
> assuming Mongo would work, but I wouldn't do that blindly. I don't know
> enough about lightcouch to know
I updated the Eclipse JPA jar earlier today...
Nick, are you around still?
How can we unit test our MongoDB and CouchDB code?
Gary
On Thu, Sep 11, 2014 at 3:03 PM, Matt Sicker wrote:
> Whoops, sort of forgot. It would be safe to upgrade EclipseLink. I'm
> assuming Mongo would work, but I woul
Whoops, sort of forgot. It would be safe to upgrade EclipseLink. I'm
assuming Mongo would work, but I wouldn't do that blindly. I don't know
enough about lightcouch to know if it's a safe upgrade, so I'll take a more
close look at their changelog.
On 11 September 2014 10:08, Gary Gregory wrote:
ping?
Gary
On Wed, Sep 3, 2014 at 9:15 AM, Matt Sicker wrote:
> I'll try to take a better look into this sometime this week. I'm pretty
> sure the JPA things should be good. I'll take a look at the unit tests for
> log4j-nosql a bit better to see if we can safely upgrade.
>
>
> On 2 September 2
I'll try to take a better look into this sometime this week. I'm pretty
sure the JPA things should be good. I'll take a look at the unit tests for
log4j-nosql a bit better to see if we can safely upgrade.
On 2 September 2014 09:24, Matt Sicker wrote:
> The JPA/EclipseLink update should be fine
The JPA/EclipseLink update should be fine to test. There are a bunch of
tests involving JPA and HSQL or H2 (can't remember which).
As to the NoSQL ones, other than integration testing, so far we can only
mock them. With something like Gora or Hazelcast or something more generic,
it's possible to u
Hi All and Nick:
I see that these updates could be done:
mongo-java-driver 2.12.3 <- 2.11.2
lightcouch 0.1.3 <- 0.0.6
org.eclipse.persistence.jpa 2.5.2 <- 2.5.1
But our unit tests do not seem very deep in NoSQL land.
Can Nick or some else set up for better testing confirm that these updates
are
10 matches
Mail list logo
