Clarify type names in analysis server API.

pkg/analysis_server/test/integration/integration_test_methods.dart

 // Copyright (c) 2014, the Dart project authors.  Please see the AUTHORS file
 // for details. All rights reserved. Use of this source code is governed by a
 // BSD-style license that can be found in the LICENSE file.
 //
 // This file has been automatically generated.  Please do not edit it manually.
 // To regenerate the file, use the script
 // "pkg/analysis_server/spec/generate_files".
 
 /**
  * Convenience methods for running integration tests
@@ skipping 1054 matching lines @@
    * file ( FilePath )
    *
    *   The file containing the errors for which fixes are being requested.
    *
    * offset ( int )
    *
    *   The offset used to select the errors for which fixes will be returned.
    *
    * Returns
    *
-   * fixes ( List<ErrorFixes> )
+   * fixes ( List<AnalysisErrorFixes> )
    *
    *   The fixes that are available for each of the analysis errors. There is a
    *   one-to-one correspondence between the analysis errors in the request and
    *   the lists of changes in the response. In particular, it is always the
    *   case that errors.length == fixes.length and that fixes[i] is the list of
    *   fixes for the error in errors[i]. The list of changes corresponding to
    *   an error can be empty if there are no fixes available for that error.
    */
   Future sendEditGetFixes(String file, int offset, {bool checkTypes: true}) {
     Map<String, dynamic> params = {};
@@ skipping 368 matching lines @@
       case "debug.launchData":
         expect(params, isDebugLaunchDataParams);
         _onDebugLaunchData.add(params);
         break;
       default:
         fail('Unexpected notification: $event');
         break;
     }
   }
 }