refactor test to consider reconnect() async behaviour

Author: Mohit Tejani

test/dist/web-titanium.test.js

@@ -155,24 +155,17 @@ describe('#distribution test (titanium)', function () {
     pubnub.reconnect();
 
     var finished = false;
-    var sawConnected = false;
 
     pubnub.addListener({
       status: function (st) {
         try {
-          // Reconnect finishes asynchronously: first status is often PNSubscribeOperation (connected).
-          // Wait until connected, then unsubscribe, then assert on the leave request (PNUnsubscribeOperation).
-          if (!sawConnected) {
-            if (st.category === PubNub.CATEGORIES.PNConnectedCategory) {
-              sawConnected = true;
-              pubnub.unsubscribe({ channels: [myChannel1] });
-            }
-            return;
-          }
-          if (st.operation !== 'PNUnsubscribeOperation') {
+          if(st.category === 'PNConnectedCategory') {
+            // this is expected due to async nature of the reconnect()
             return;
           }
+          expect(st.category).to.be.equal('PNDisconnectedCategory');
           if (!finished) {
+            // prevent calling done twice
             finished = true;
             done();
           }
@@ -181,5 +174,6 @@ describe('#distribution test (titanium)', function () {
         }
       },
     });
+    pubnub.unsubscribe({ channels: [myChannel1] });
   });
 });