Proposing SQL Statement Coverage Metrics: Difference between revisions
Programsam (talk | contribs) |
Programsam (talk | contribs) |
||
| Line 125: | Line 125: | ||
statements. | statements. | ||
'''Server-side target statement coverage = '''PLACEHOLDER''' | '''Server-side target statement coverage''' = '''PLACEHOLDER''' | ||
where Test(''t'') is a SQL statement tested at least once. | where Test(''t'') is a SQL statement tested at least once. | ||
'''Coverage interpretation''': A low value for target statement coverage indicates that testing was insufficient. Programmers need to add more test cases to the input validation set for untested SQL statements to improve target statement coverage. | '''Coverage interpretation''': A low value for target statement coverage indicates that testing was insufficient. Programmers need to add more test cases to the input validation set for untested SQL statements to improve target statement coverage. | ||
=== 3.2 Input Variable Coverage === | |||
Input variable coverage measures the percentage of input variables used in at least one test at the server-side. Input variable coverage does not consider all the constraints for the input variable. | |||
'''Definition''': A set of tests satisfies input variable coverage criterion if and only if for every input variable f ∈ F, there exists at least one test that uses that input variable at least once. | |||
'''Metric''': The input variable coverage criterion can be measured by the percentage of input variables tested at least once by the test set out of total number of input variables found in any target statement in the production code of the system. | |||
== 9. References == | == 9. References == | ||