Inconclusive viability tests
We currently treat InventoryViablity
as finished when there exists a value in percentViable
. This allows only for two states a test can be in: pending and completed. In viability testing, the result of the final of any test may be conclusive or inconclusive.
In this ticket we add a status
enum to InventoryViability
with the following options: PENDING
, CONCLUSIVE
, INCONCLUSIVE
. The initial state is PENDING
. For existing records in the database, the state is set to CONCLUSIVE
, but it may be updated by the database manager to INCONCLUSIVE
based on notes or other available information.
The user will need to choose between CONCLUSIVE
and INCONCLUSIVE
when finalizing the test.
Aspects
Update InventoryTriggers#upsertSeedInventoryExtraWithLatestViability()
so that only CONCLUSIVE
tests are considered.