DRAFT: GraphQL updates based on issue #406

[alflennik]

This PR proposes GraphQL schema changes for issue #406. Some changes might not be obvious from reading the diff:

• Giving TestResults their own table, instead of continuing to store them as JSON data in the TestPlanRun table. This will permit setting up Postgres associations between each TestResult and the AT and Browser versions.
• Giving Tests a table as well, which will keep the Test model symmetrical with the TestResult model.
• The FindOrCreateTestPlanReport mutation will no longer automatically create atVersions and browserVersions, since mutations are being added to explicitly manage these.

[howard-e]

Thanks for looking at this so quickly! I know this is still marked as a draft but was wondering if this shouldn't include atVersion and browserVersion as well?

[alflennik]

Thank YOU for looking at this so quickly 😁 So, splitting up the At / Browser and AtVersion / BrowserVersion is intentional - I put the atVersion and browserVersion fields on the TestResult type. This means that reports are locked to an AT and Browser, but they're no longer locked to an exact version. And now each TestResult can have slightly different versions. Let me know if you imagined something different maybe?

[alflennik]

Closed because Erika took this one over the finish line!