tree 08f8077bf878703a85334201d4a946c2f6d5f154
parent 696e37a845b8d21a061786140ba17a22f8e6463a
author srawlins <srawlins@google.com> 1591916316 -0400
committer Sam Rawlins <sam.rawlins@gmail.com> 1594309593 -0700

MockBuilder: Refactor exception-throwing paths; add more

* Almost all sanity checking was done in the _MockLibraryInfo constructor.
  Yuck. Move this to a new method.
* Throw when a mock of the same name already exists. Someone is likely
  migrating existing tests, and would be in for a surprise.
* Throw when asked to generate for two unique classes which have the same
  name. The code-generating API does not yet have a mechanism for
  user-supplied names to avoid such a conflict.
* Test that the GenerateMocks annotation can be written multiple times, and
  that mocks from each occurrence are generated.
* Check that `entryLib` is not null. I can't reproduce this in a test, but
  encountered it while testing on a real test: tableview_test.dart.
* Deduplicate classes which are asked to be mocked multiple times.

PiperOrigin-RevId: 315995820