Fix(grunt): protractor fixed to work again, grunt options in readme

Author: PaulL1

DEVELOPER.md

@@ -18,9 +18,11 @@ http://localhost:9003/docs/#/tutorial to browse each tutorial.
 <br/>options
 <br/> no-e2e - eliminate protractor tests
 <br/> angular=n.n.n - specify a specify angular version to run unit tests against
+<br/> core - run only the tests for the core code, skip features
+<br/> fast - alias for --no-e2e --core --angular=1.3.7
 
 ```
-grunt dev --no-e2e --angular=1.2.16
+grunt dev --no-e2e --angular=1.3.7
 ```
 
 # Code Structure

FIRST_TIMER.md

@@ -145,7 +145,9 @@ Check that the tutorials are working fine on your local install.
 
 __Pro-tip:__ Running grunt dev can be slow, as it automatically runs all e2e tests and
 unit tests on each change.  You can just skip the testing by running instead `grunt dev --no-e2e`, which
-makes it faster, but gives you less information about where you may have broken things.  
+makes it faster, but gives you less information about where you may have broken things.  You
+can also use `grunt dev --fast`, which runs only the core unit tests, skips e2e testing, and runs
+unit tests against only the most recent angular version (it's an alias for `grunt dev --core --no-e2e --angular=1.3.7`).  
 Or you can edit the tests to target only the specific tests for the area you're working on.
 Pick the tutorial that has e2e tests and is most relevant to the area you're working in,
 and edit the e2e test to have `ddescribe` rather than `describe`.  This will ask jasmine

README.md

@@ -84,6 +84,14 @@ You can also use the `--browsers` specify what browsers to test with (PhantomJS
 By default the `dev` tasks runs e2e tests with protractor. If you have problems with them running slow or hanging, you can disable them with the `--no-e2e` flag:
 
     > grunt dev --no-e2e
+    
+The grunt task is getting slower as the body of tests gets larger.  If you're only working on the core functionality you can disable the unit tests on the features with the `--core` flag:
+
+    > grunt dev --core
+    
+As a shortcut for options that the developers frequently use, there is also a `--fast` flag, which equates to `--core --no-e2e --angular=<latest>`:
+ 
+    > grunt dev --fast
 
 ## Karmangular
 

grunt/watch.js

@@ -22,7 +22,7 @@ module.exports = function( grunt, options ){
 
     protractor: {
       files: ['.tmp/doc-scenarios/**/*.spec.js', 'test/e2e/**/*.spec.js'],
-      tasks: ['ngdocs', 'protractor-watch:auto']
+      tasks: ['protractor-watch:auto']
     },
 
     less: {
@@ -51,7 +51,7 @@ module.exports = function( grunt, options ){
     }
   };
 
-  if (grunt.option('fast') || !grunt.option('e2e')){
+  if (grunt.option('fast') || grunt.option('e2e') === false){
     config.protractor.tasks = ['ngdocs'];
   }
 

misc/tutorial/105_footer.ngdoc

@@ -96,9 +96,9 @@ You can override the default grid footer template with gridOptions.footerTemplat
       it('grid should have footers with specific values', function () {
         gridTestUtils.expectFooterCellValueMatch( 'grid1', 0, '' );
         gridTestUtils.expectFooterCellValueMatch( 'grid1', 1, 'total: 281568' );
-        gridTestUtils.expectFooterCellValueMatch( 'grid1', 2, '30.196' );
+        gridTestUtils.expectFooterCellValueMatch( 'grid1', 2, '30.248' );
         gridTestUtils.expectFooterCellValueMatch( 'grid1', 3, 'min: 20' );
-        gridTestUtils.expectFooterCellValueMatch( 'grid1', 4, 'max: 40' );
+        gridTestUtils.expectFooterCellValueMatch( 'grid1', 4, 'max: 49' );
         gridTestUtils.expectFooterCellValueMatch( 'grid1', 5, 'custom template' );
         // gridTestUtils.expectFooterCellValueMatch( 'grid1', 6, 'max: ' + getMaxDateString() );
         // TODO: need to check item count, not done