[riot-notifications] [RIOT-OS/RIOT] RFC: Use RobotFramework to write RIOT tests (#10241)
notifications at github.com
Fri Nov 23 17:21:59 CET 2018
> Another part of this work is to introduce a good, solid, standard test framework.
We don't introduce a framework in order to have a framework.
> As you may have further taken notice, this already led to a series of critical bug discoveries and repairs for the I2C rework and the latest release. Does this explain the context?
The I2C testing is awesome, but it doesn't at all require a "testing framework". After all the python abstraction that Robot Framework requires, the I2C tests could've been expressed as pure-python scripts in half the lines, with the tests producing the same useful results.
I don't want to argue against introducing a testing framework. I'd just like to see proper reasoning.
We've already established that writing the test cases themselves is highly subjective in terms of preferred languages. Currently we're converging towards "framework X has nicer output", which sounds somewhat irrelevant to me.
You're claiming that by using a "good, solid, standard test framework" we're putting testing on "systematic, professional ground". How? Why is it currently unprofessional or unsystematic, and how is a framework changing that?
What are the functional requirements of a testing framework for RIOT? How is what we have not fulfilling those?
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications