Fix built-in controller registration flow.

Built-in controller registration flow is wrong, breaking the use
case where more than one test class is executed in a test run.
It should follow the same flow as controller modules registered
by the test classes.

The import, registration, and unregistration should happen once for
each test class in each test run, for all controller modules.

Added a unit test for this use case as well.

Bug=29196491

Change-Id: Icdda688e8569686589b27a7234ea982401f4eb9d
2 files changed
tree: 3a1b8452c7005be470cc064b77072db508403d7e
  1. acts/