diff --git a/.travis.yml b/.travis.yml
index 6d7a36ebe1..4a0c82771a 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -77,7 +77,7 @@ jobs:
       before_install: true
       install: npm install --production
       name: 'Latest Node.js'
-      script: ./bin/mocha --no-config --reporter spec test/sanity/sanity.spec.js
+      script: ./bin/mocha --no-config --reporter spec test/smoke/smoke.spec.js
       cache:
         directories:
           - ~/.npm
diff --git a/test/sanity/sanity.spec.js b/test/sanity/sanity.spec.js
deleted file mode 100644
index 59d5896515..0000000000
--- a/test/sanity/sanity.spec.js
+++ /dev/null
@@ -1,9 +0,0 @@
-'use strict';
-
-var assert = require('assert');
-
-describe('a production installation of Mocha', function() {
-  it('should be able to execute a test', function() {
-    assert.ok(true);
-  });
-});
diff --git a/test/smoke/smoke.spec.js b/test/smoke/smoke.spec.js
new file mode 100644
index 0000000000..7f1365f33e
--- /dev/null
+++ b/test/smoke/smoke.spec.js
@@ -0,0 +1,15 @@
+'use strict';
+
+// This test ensures Mocha's dependencies are properly in place,
+// and is intended to be run after an `npm install --production` in a clean
+// working copy. It helps avoid publishing Mocha with `dependencies`
+// in `devDependencies` or otherwise in the wrong place.
+// It does not ensure that all files are present in the published package!
+
+var assert = require('assert');
+
+describe('a production installation of Mocha', function() {
+  it('should be able to execute a test', function() {
+    assert.ok(true);
+  });
+});