Update guide for 2.3.0 and fix final tests

Author: drew-gross

2.3.0.md

@@ -8,14 +8,13 @@ If you are using MongoDB in Cluster or Replica Set mode, we recommend reading Mo
 // Select the database that your Parse App uses
 use parse;
 
-// Select the collection your Parse App uses for users. For migrated apps, this probably include a collectionPrefix.
+// Select the collection your Parse App uses for users. For migrated apps, this probably includes a collectionPrefix.
 var coll = db['your_prefix:_User'];
 
 // You can check if the indexes already exists by running coll.getIndexes()
 coll.getIndexes();
 
 // The indexes you want should look like this. If they already exists, you can skip creating them.
-/*
 {
   "v" : 1,
   "unique" : true,
@@ -39,7 +38,6 @@ coll.getIndexes();
   "background" : true,
   "sparse" : true
 }
-*/
 
 // Create the username index.
 // "background: true" is mandatory and avoids downtime while the index builds.
@@ -56,11 +54,11 @@ There are some issues you may run into during this process:
 
 ## Mongo complains that the index already exists, but with different options
 
-In this case, you will need to create the unique index using a different index name, and/or remove the incorrect index. Avoid downtime or a temporary performance regression in your app by building the new index before removing the old one.
+In this case, you will need to remove the incorrect index. If your app relies on the existence of the index in order to be performant, you can create a new index, with "-1" for the direction of the field, so that it counts as a different options. Then, drop the conflicting index, and create the unique index.
 
 ## There is already non-unique data in the username or email field
 
-This is possible if you have explicitly set some user's emails to null. These null emails can be removed with this command:
+This is possible if you have explicitly set some user's emails to null. If this is bogus data, and those null fields shoud be unset, you can unset the null emails with this command. If your app relies on the difference between null and unset emails, you will need to upgrade your app to treat null and unset emails the same before building the index and upgrading to Parse Server 2.3.0.
 
 ```js
 coll.update({ email: { $exists: true, $eq: null } }, { $unset: { email: '' } }, { multi: true })
@@ -69,7 +67,3 @@ coll.update({ email: { $exists: true, $eq: null } }, { $unset: { email: '' } },
 ## There is already non-unique data in the username or email field, and it's not nulls
 
 This is possible due to a race condition in previous versions of Parse Server. If you have this problem, it is unlikely that you have a lot of rows with duplicate data. We recommend you clean up the data manually, by removing or modifying the offending rows.
-
-## My app depends on emails set to null behaving differently from emails set to undefined
-
-You will need to update your app before executing the previous steps.

spec/ParseAPI.spec.js

@@ -252,8 +252,8 @@ describe('miscellaneous', function() {
       return Parse.User.logIn('test', 'moon-y');
     }).then((user) => {
       expect(user.get('foo')).toEqual(2);
-      Parse.User.logOut();
-      done();
+      Parse.User.logOut()
+      .then(done);
     }, (error) => {
       fail(error);
       done();
@@ -371,8 +371,8 @@ describe('miscellaneous', function() {
       expect(results.length).toEqual(1);
       expect(results[0]['foo']).toEqual('bar');
       done();
-    }).fail(err => {
-      fail(err);
+    }).fail(error => {
+      fail(JSON.stringify(error));
       done();
     })
   });

src/testing-routes.js

@@ -14,6 +14,7 @@ function createApp(req, res) {
   var appId = cryptoUtils.randomHexString(32);
 
   ParseServer({
+    databaseURI: 'mongodb://localhost:27017/parseServerMongoAdapterTestDatabase',
     appId: appId,
     masterKey: 'master',
     serverURL: Parse.serverURL,