It turns out that EF was set up to utilise Automatic Migrations rather than our own migrations while performing integration tests. As a result of the calculated columns being inserted in a unique SQL script across the
the columns weren't really used as a migration technique
columns throughout the testing, but they were really produced by EF as ordinary
fields that cannot be null. Therefore, when attempting to add a new model to the context, EF was inserting
bursting into the columns.
The migrations should really be executed in the integration tests as a solution. After the column has been calculated, EF stops keeping track of it.