SERVER-12127 migrate js tests to jscore suite when not related to writes

Moved test jstest/[a-i].js -> jstests/core/ and made changes to comply with write command api

1 files changed, 26 insertions, 0 deletions

diff --git a/jstests/core/arrayfind6.js b/jstests/core/arrayfind6.js
new file mode 100644
index 00000000000..f4531cea96a
--- /dev/null
+++ b/jstests/core/arrayfind6.js
@@ -0,0 +1,26 @@
+// Check index bound determination for $not:$elemMatch queries.  SERVER-5740
+
+t = db.jstests_arrayfind6;
+t.drop();
+
+t.save( { a:[ { b:1, c:2 } ] } );
+
+function checkElemMatchMatches() {
+    assert.eq( 1, t.count( { a:{ $elemMatch:{ b:1, c:2 } } } ) );
+    assert.eq( 0, t.count( { a:{ $not:{ $elemMatch:{ b:1, c:2 } } } } ) );
+    assert.eq( 1, t.count( { a:{ $not:{ $elemMatch:{ b:1, c:3 } } } } ) );
+    assert.eq( 1, t.count( { a:{ $not:{ $elemMatch:{ b:{ $ne:1 }, c:3 } } } } ) );
+    // Index bounds must be determined for $not:$elemMatch, not $not:$ne.  In this case if index
+    // bounds are determined for $not:$ne, the a.b index will be constrained to the interval [2,2]
+    // and the saved document will not be matched as it should.
+    assert.eq( 1, t.count( { a:{ $not:{ $elemMatch:{ b:{ $ne:2 }, c:3 } } } } ) );
+}
+
+checkElemMatchMatches();
+t.ensureIndex( { 'a.b':1 } );
+checkElemMatchMatches();
+
+// We currently never use an index for negations of
+// ELEM_MATCH_OBJECT expressions.
+var explain = t.find( { a:{ $not:{ $elemMatch:{ b:{ $ne:2 }, c:3 } } } } ).explain();
+assert.eq( "BasicCursor", explain.cursor );