On Wed, 2016-11-30 at 09:38 +0100, Josef Skladanka wrote:
So if this is what you wanted to do (data validation), it might be a good idea to have that submitter middleware.
Yeah, that's really kind of the key 'job' of that layer. Remember, we're dealing with *manual* testing here. We can't really just have a webapp that forwards whatever the hell people manage to stuff through its input fields into ResultsDB.
Really there's two kinds of 'validation' going on, if you'd like to think of it that way: we need to tell the web UI 'these are the possible scenarios for which you should prompt users to input results at all' (which for release validation is all the 'notice there's a new compose, combine it with the defined release validation test cases and expose all that info to the UI' work), and we need to take the data the web UI generates from user input, make sure it actually matches up with the schema we decide on for storing the results before forwarding it to resultsdb, and tell the web UI there's a problem if it doesn't.
That's how I see it, anyhow. Tell me if I seem way off. :)