Re:Why was "goto fail;" added without any other change to th...
by homakov on Friday February 28, 2014 @10:12AM
(#7319082)
Not testing everywhere, but "smoking test" that your SSL implementation protects from MITM, at all, and none of your programmers screwed it (with gotofail or anything else).
This is what I expect from an OS developers
Re:Why was "goto fail;" added without any other change to th...
by raverbashing on Friday February 28, 2014 @10:17AM
(#7319124)
Yes, something that would test all the steps of the SSL authentication and possible failures
Maybe the people from OpenSSL have some test like that already
Re:Why was "goto fail;" added without any other change to th...
by nailer on Friday February 28, 2014 @10:10AM
(#7319073)
Ack re: TDD, but integration tests with a bad certificate would have picked this up.
Re:Why was "goto fail;" added without any other change to th...
by stcredzero on Friday February 28, 2014 @10:12AM
(#7319084)
And sometimes impossible
I've been in that position. Sometimes with embedded, you can't have software fixtures, only hardware ones. (Bit banging)
Re:Why was "goto fail;" added without any other change to th...
by raverbashing on Friday February 28, 2014 @10:22AM
(#7319158)
Tell me about it
And you think you know what the device answers and understands, but there's usually some gotchas.
And sometimes impossible
In Python/Ruby sure, it's easy. In Java, or even C++, it's doable, but not great, and it requires some heavy tricks.
But they surely need tests, but not necessarily TDD.