7 comments:
File Documentation/technotes/2019-12-firmware-testing.md:
This lava? https://minecraft.gamepedia. […]
no, added the link.
Patch Set #3, Line 20: test host
Would be nice if the test host could be in control of more than one DUT. […]
Ack on driving multiple DUTs (added). As for network, I consider that outside the scope of the test runner itself. I think that relying on network for test communication only adds complexity (which side failed configuring its network _this_ time?). The idea is to tailor this around the barest minimum of components and, incidentally, cut down on log sizes as well (the logs we get from Chromium OS' test infra are gigantic, and I can't claim that this improves anything).
It may also be augmented by additional circuitry that
allows automating these steps.
That's exactly the only thing I've done of my automated test setup. […]
so my plan will be to provide (compile-time) pluggable modules for that, and driving two kinds myself: the manual operator UI (on some random DUT I have here) and integration with Chrome OS' servo tools.
Patch Set #3, Line 39: So these are
Seems like something went missing here?
"So these are ... Requirement 1 ... and ... Requirement 2", maybe I got overboard with being fancy here? ;-)
?
see above.
Patch Set #3, Line 106: The language should be popular and the implementation robust.
Required already below?
I styled the doc in having prose explaining the properties and with requirements extracted from them interspersed. You're right that the direct repetition isn't helpful though. Hmm...
Patch Set #3, Line 147: set up
set-up/setup?
Done
To view, visit change 37643. To unsubscribe, or for help writing mail filters, visit settings.