When addSource() in tests, call both addFile() and changeFile().

pkg/analysis_server/test/abstract_context.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.
 
 library testing.abstract_context;
 
 import 'dart:async';
 
 import 'package:analyzer/dart/ast/ast.dart';
 import 'package:analyzer/dart/element/element.dart';
@@ skipping 68 matching lines @@
   Source addPackageSource(String packageName, String filePath, String content) {
     packageMap[packageName] = [(newFolder('/pubcache/$packageName'))];
     File file = newFile('/pubcache/$packageName/$filePath', content);
     return file.createSource();
   }
 
   Source addSource(String path, String content, [Uri uri]) {
     File file = newFile(path, content);
     if (enableNewAnalysisDriver) {
       driver.addFile(path);
+      driver.changeFile(path);

[Brian Wilkerson, 2017/02/09 16:43:54]

Should `addFile` be extended to also always do the work done by `changeFile`, or
are there places where it makes sense so call `addFile` without calling
`changeFile`?

[scheglov, 2017/02/09 16:48:03]

In general - no.
We just allow us to be a bit sloppy in tests.

       _fileContentOverlay[path] = content;
       return null;
     } else {
       Source source = file.createSource(uri);
       ChangeSet changeSet = new ChangeSet();
       changeSet.addedSource(source);
       context.applyChanges(changeSet);
       context.setContents(source, content);
       return source;
     }
@@ skipping 102 matching lines @@
  * [engine.GeneralizingElementVisitor].
  */
 class _ElementVisitorFunctionWrapper extends GeneralizingElementVisitor {
   final _ElementVisitorFunction function;
   _ElementVisitorFunctionWrapper(this.function);
   visitElement(Element element) {
     function(element);
     super.visitElement(element);
   }
 }