artifically low 'nodes asserted' % under test suite coverage
First, look at contract coverage for our project:
We're very close to 100% node coverage for all responses in the WSDL, and have tried to create assertions for all response elements, too. While it is possible we missed a few elements, it is doubtful that we would have assertions for only 16%, when node coverage is so high.
So why is assertion coverage so low - 16% - when we have the responses covered so well?
I have two theories for the artificially low asserted nodes %:
1. soapui is including request nodes, which are not assert-able, in the denominator
2. soapui is including excluded elements in the denominator
Anyway, is it possible for us to get a more accurate value for nodes asserted?
We're very close to 100% node coverage for all responses in the WSDL, and have tried to create assertions for all response elements, too. While it is possible we missed a few elements, it is doubtful that we would have assertions for only 16%, when node coverage is so high.
So why is assertion coverage so low - 16% - when we have the responses covered so well?
I have two theories for the artificially low asserted nodes %:
1. soapui is including request nodes, which are not assert-able, in the denominator
2. soapui is including excluded elements in the denominator
Anyway, is it possible for us to get a more accurate value for nodes asserted?
