[CXX-388] Test against MongoDB 2.2 and 2.0 on MCI Created: 03/Nov/14 Updated: 23/Jan/15 Resolved: 22/Jan/15 |
|
| Status: | Closed |
| Project: | C++ Driver |
| Component/s: | Testing |
| Affects Version/s: | None |
| Fix Version/s: | legacy-1.0.0-rc4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tyler Brock | Assignee: | Adam Midvidy |
| Resolution: | Done | Votes: | 0 |
| Labels: | legacy-cxx | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
As part of merging Mongo-Orchestration into our testing framework we needed to temporarily disable testing against MongoDB 2.2 because orchestration is having trouble starting mongod. I think this is because 2.2 and older server versions do not accept "setParameter" as an argument and a fix requires a bit of work to plumb through. We could re-enable testing on 2.2 and 2.0 (since we know the driver already passes against them) by passing an "old-server" flag to scons which will invoke the tests in a way that does not attempt to enableTestCommands via setParameter (to be determined by implementer, but most likely via an additional argument to integration_test_main). That additional argument to the integration tests would tell orchestration to avoid starting mongod with "--setParameter=enableTestCommands=1". Note: The tests we have written that depend on test commands being enabled already know to skip themselves if running on 2.2 or earlier. |
| Comments |
| Comment by Githook User [ 22/Jan/15 ] |
|
Author: {u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}Message: |
| Comment by Githook User [ 22/Jan/15 ] |
|
Author: {u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}Message: |
| Comment by Adam Midvidy [ 22/Jan/15 ] |
| Comment by Adam Midvidy [ 16/Jan/15 ] |
|
The necessary functionality has been merged into MO (https://github.com/10gen/mongo-orchestration/pull/158) so I am going to move this forward. |
| Comment by Tyler Brock [ 16/Nov/14 ] |
|
On second thought I'm thinking we shouldn't do this at all. This is the type of abstraction that should be done at the orchestration layer not in driver tests. For us to spend time baking this into the test code would be a waste. |