Mongo 3.0 compatibility test coverage

[philfreo]

monoengine isn't compatible with Mongo 3.0

For example #629

But I wouldn't be surprised if there were other issues also. Would be awesome if this library were well-tested against 3.0.

[rozza]

will need the latest pymongo - see: http://api.mongodb.org/python/current/changelog.html#changes-in-version-2-8

[MRigal]

many people are using Mongoengine with Mongo 3.0 in production, even with mongoengine versions launched before, so it is not correct say it is not compatible with Mongo 3.0. Even the issue you pointed to is not related to Mongo 3.0.

However, testing against different MongoDB versions would be great. But if it is not doable, what should we do?

[mmellison]

I believe the fundamental question here is this:

Is it necessary to test MongoEngine with different MongoDB versions for compatibility, or is testing with the different version of PyMongo enough to cover compatibility with different MongoDB versions?

[MRigal]

The answer is currently NO. PyMongo is not enough to cover compatibility. At least until we have some functionalities and/or tests which are based on adminCommand output for Mongo. However, the not covered part is extremely minimal

[mmellison]

Okay, then there is really nothing stopping us from installing a different version of MongoDB via Travis (I saw it done about a year ago). The only problem, I anticipate that the job times are going to explode and possibly more false positives due to environment failures.

[MRigal]

Yes, I think also... It would be good to have that restricted only to
release builds for example...

2015-04-30 15:28 GMT+02:00 Matthew Ellison notifications@github.com:

Okay, then there is really nothing stopping us from installing a different
version of MongoDB via Travis (I saw it done about a year ago). The only
problem, I anticipate that the job times are going to explode and possibly
more false positives due to environment failures.

—
Reply to this email directly or view it on GitHub
#861 (comment)
.

[dpercy]

I anticipate that the job times are going to explode

You wouldn't have to test every combination of PyMongo and MongoDB versions. Some combinations aren't supported anyway: https://docs.mongodb.com/ecosystem/drivers/driver-compatibility-reference/#python-driver-compatibility

Maybe each version of pymongo that Travis tests could run against the latest compatible version of MongoDB:

• pymongo 2.7 with mongodb 2.6
• pymongo 2.8 with mongodb 3.0
• pymongo 3.0 with mongodb 3.0
• pymongo 3.2 with mongodb 3.2

What do you think?

[lafrech]

Could be worth trying. Would you like to makes those changes and see how long the builds take?

If time is an issue, maybe the number of MongoDB versions can be restricted to just 2.6 and 3.2, for instance.

[Gallaecio]

Can you append "testing", "coverage" or something like that to the title? I believe it is misleading right now.

[bagerard]

Closing this as it was integrated in travis a while ago