TestResult: Don't default to NOT_EXECUTED

We need to differentiate between the result states of "nothing has
set the result state" and "the result state was explicitly set to
NOT_EXECUTED (via testIgnored() or testAssumptionFailure()).

This allows us to properly report NOT_EXECUTED results from our
testing infrastructure.

Bug: 28240017
Change-Id: If6617cc8dea46d2fa0f6404882222c09daac55a0
2 files changed