diff --git a/clients/web/test/spec/collectionSpec.js b/clients/web/test/spec/collectionSpec.js
index <HASH>..<HASH> 100644
--- a/clients/web/test/spec/collectionSpec.js
+++ b/clients/web/test/spec/collectionSpec.js
@@ -163,10 +163,18 @@ describe('Test collection actions', function () {
             return $('.g-collection-actions-button').length > 0;
         }, 'collection view to load');
 
-        waits(200);
+        waitsFor(function () {
+            return $('.g-loading-block').length == 0;
+        }, 'for all blocks to load');
 
         runs(function () {
             $('.g-collection-actions-button').click();
+        });
+
+        waitsFor(function () {
+            return $('.g-delete-collection:visible').length > 0;
+        }, 'delete button to appear');
+        runs(function () {
             $('.g-delete-collection').click();
         });
The web client collection test would intermittently fail.  This appears to be that the collection actions could appear before the collection information, which led to asking for a delete being in a strange state.  I changed this to wait until all of the g-loading-block classed elements are gone, which appears to be sufficient in this case.