stronk7
commented
10 years ago Aha, I really haven't looked inside run files (doing it now).
My main point about this is that we could decide to store all those results somewhere and perform some alternative data crunching different from current one (comparing two runs).
Things like showing along the time how every "base" evolves, or showing the results like test failures (converting to xUnit format)... are two simple ideas about what we could expect from exported data.
But, after looking to current format (var_export, it seems), surely it's enough to be able to perform those different "reports". So you can consider this to be closed, as far as they may be enough.
Just a silly comment... looking at current runs format... could we improve it a bit and normalize things like: $baseversion, $siteversion, $sitecommit ? Right now each one has its own format, and it would be far better to have both the base and site commits, and then, if needed, the base and site versions and/or the base and site releases.. but each one inside its own variable (instead of current "mix").
dmonllao
Many things to discuss here... Runs data is all contained in PHP files, one per run, so the fastest way to code it would be allowing exports & imports of those .php files.
I doubt whether it is worth to invest resources in creating a new import/export format as those files are pretty readable, containing the run data at the beginning. Waiting for feedback.