Moved property tests to the main suite

Property tests can only run in Node, so they were previously in another
directory that only gets run in Node. Now they're next to the related
non-property tests and marked pending in the browser. This makes it more
likely that a developer who normally only runs tests in the browser will
notice and run them.

spec/support/jasmine-browser.js

@@ -15,7 +15,7 @@ module.exports = {
     '**/*.js'
   ],
   specDir: 'spec',
-  specFiles: ['**/*[Ss]pec.js', '!npmPackage/**/*', '!property/**/*'],
+  specFiles: ['**/*[Ss]pec.js', '!npmPackage/**/*'],
   helpers: [
     'helpers/asyncAwait.js',
     'helpers/BrowserFlags.js',
@@ -26,6 +26,7 @@ module.exports = {
     'helpers/domHelpers.js',
     'helpers/integrationMatchers.js',
     'helpers/promises.js',
+    'helpers/requireFastCheck.js',
     'helpers/defineJasmineUnderTest.js'
   ],
   random: true,

spec/support/jasmine.json

@@ -2,7 +2,6 @@
   "spec_dir": "spec",
   "spec_files": [
     "core/**/*[Ss]pec.js",
-    "property/**/*[Ss]pec.js",
     "npmPackage/**/*[Ss]pec.js"
   ],
   "helpers": [
@@ -14,6 +13,7 @@
     "helpers/domHelpers.js",
     "helpers/integrationMatchers.js",
     "helpers/promises.js",
+    "helpers/requireFastCheck.js",
     "helpers/nodeDefineJasmineUnderTest.js"
   ],
   "random": true