Test asset updates process

[jscholes]

There are a number of changes to be made to the test format, both to support test writers better and facilitate the goals of the automation workstream. These changes may be made all at once in a single sprint, or spread out across a larger timeframe.

Either way, they won't be the last changes proposed for the test format over time. As such, we need a clear, documented process for updating existing tests when the test format changes. Some areas for discussion that spring to mind are:

• Should the test format be versioned in some way, so that the test runner can execute older tests that haven't yet been updated?
• How much can we rely on automation versus human effort for application of updates?
• Do we need a human review process for updated test plans, and if so, how should that be coordinated?
• Can we take this opportunity, during the work on updates, to clearly document the test format? The documentation on the wiki isn't as helpful as it could be.

I welcome any further input.