On Sat, Sep 24, 2011 at 10:05:36PM -0400, Pavel Ivanov wrote:
No, that's exactly the point that Richard tries to explain to you and
you don't seem to understand. SQLite's testing coverage is a coverage
of the resulting object code, not some source code lines. And so it
Yes, I now realize that
On Fri, Sep 23, 2011 at 10:26:43PM -0400, Pavel Ivanov wrote:
if (A || 1) ...
You can get (e) by giving test cases for A and !A, but most certainly
flipping A does not independently affect the outcome as required by
the plain reading of (f).
I'm pretty sure that the latest versions
On Sat, Sep 24, 2011 at 04:58:35AM +0300, Sami Liedes wrote:
On Fri, Sep 23, 2011 at 09:17:43PM -0400, Richard Hipp wrote:
--
1. Structural coverage guidelines are:
a) Every statement in the program has been invoked at least once;
b) Every point of entry and exit
On Fri, Sep 23, 2011 at 11:16:37AM -0400, Richard Hipp wrote:
Opinions vary on the exact meaning of MC/DC for a language (such as C) that
has short-circuit boolean operators. You are advocating a more rigorous
view of MC/DC that what I have heard before. This is not to say it is
wrong, only
[Note: In case my explanations are not clear enough, there's a fairly
formal position paper by Certification Authorities Software Team
(CAST-10) clarifying MC/DC here:
http://www.faa.gov/aircraft/air_cert/design_approvals/air_software/cast/cast_papers/media/cast-10.pdf
]
On Fri, Sep 23,
On Fri, Sep 23, 2011 at 09:17:43PM -0400, Richard Hipp wrote:
--
1. Structural coverage guidelines are:
a) Every statement in the program has been invoked at least once;
b) Every point of entry and exit in the program has been invoked at least
once;
c) Every control
Hi!
Looking at
http://www.sqlite.org/testing.html
it seems to me that MC/DC coverage is explained wrong there. This in
turn makes me wonder if SQLite tests really have 100% MC/DC coverage
or if this claim is just based on mistaken understanding of MC/DC.
The page explains:
