Modified condition/decision coverage: Difference between revisions

Revision as of 07:57, 8 October 2020

Revision as of 00:32, 24 October 2020

Line 31:

==RC/DC==

'''Reinforced condition/decision coverage''' ('''RC/DC''') is a stronger version of the MC/DC coverage criterion, suitable for [[safety-critical system]]s.<ref>{{cite articlejournal| title=From MC/DC to RC/DC: formalization and analysis of control-flow testing criteria | first1=S.A. | last1=Vilkomir | authorlink1=Sergiy Vilkomir | first2=J.P. | last2=Bowen | authorlink2=Jonathan Bowen | journal=[[Formal Aspects of Computing]] | volume=18 | number=1 | pages=42–62 | date=2006 | publisher=[[Springer Nature]] | doi=10.1007/s00165-005-0084-7 | s2cid=10467796 }}</ref> It was originally proposed by [[Sergiy Vilkomir]] in 2002.<ref>{{cite articlejournal| title=Reinforced condition/decision coverage (RC/DC): A new criterion for software testing | first1=S.A. | last1=Vilkomir | authorlink1=Sergiy Vilkomir | first2=J.P. | last2=Bowen | authorlink2=Jonathan Bowen | workjournal=International Conference of B and Z Users | publisher=[[Springer-Verlag]] | series=[[Lecture Notes in Computer Science]] | volume=2272 | pages=291–308 | date=2002 | doi=10.1007/3-540-45648-1_15 | isbn=978-3-540-43166-4 }}</ref>

A second publication refutes this claim and indicates that MCDC (at least the Unique Cause Strong MCDC "UCMS" or Masking) variants of MCDC have superior coverage to the referenced Reinforced condition/decision coverage (RC/DC).<ref>{{cite journal |last1=Kapoor |first1=Kalpesh |last2=Bowen |first2=Jonathan P |authorlink2=Jonathan Bowen |title=A formal analysis of MCDC and RCDC test criteria |journal=Software Testing, Verification and Reliability |date=2005 |volume=15 |issue=1 |pages=21-4021–40 |doi=10.1002/stvr.306 |publisher=[[Wiley Online Library]]|s2cid=35276126 }}</ref>

==See also==