Hi,
There are 2 approaches for this, you can approach test coverage from the requirements perspective or from the code perspective.
Your questions regarding Statement coverage , Decision Coverage point towards looking at the code that is written. Now, this is absolutely a valuable approach, I can only hope that testing of airplane control systems, nuclear reactor control systems make use of these techniques. But DevTest doesn't have a lot to offer here. There is absolutely no notion at all with regards to "lines of code of the SUT" within a DevTest automation script. The only thing that would come close is installing an CAI agent inside the SUT and saving all the traces recorded. From this you could gather all methods from all classes that are called during the test. So you could get to some kind of Method Coverage (which is one level up from statement coverage) however all the cross-referencing logic with the actual classes and methods you would have to write that yourself.
The other approach is from the requirements perspective. Because for a lot of systems that are being written there is a concern with code-focused test coverage. Because with this kind of test coverage you will know how good your code is covered by your testcases but there is no guarantee that this code is actually implementing what the customer really wants. No guarantee that his actual requirements are being implemented.
Broadcom's Agile Requirements Designer is a solution that allows you to model the requirements of the system. Test coverage is then calculated based on the possible execution paths that are dictated by these requirements models and you can optimize them such that a minimal amount of testcases guarantees sufficient test coverage. And then, when the test coverage is agreed to be sufficient, the (DevTest) automation scripts are generated from the selected execution paths. So, it's the other way around, you decide on what coverage is sufficient and then the testcases are generated which validate it.
Cheers,
Danny
::DISCLAIMER::
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.