Use case 1: Calculate a metric and save result in metric history

Posted May 10th, 2007 by jfiat_es
in
References
Test Plan:
Metrics (and related)
Web page:
http://docs.google.com/Doc?id=d4st9b8_35hqfhrx
Purpose:
  • Check if there is any uncommented features in the code.
  • Use a pre-defined metrics called "Uncommented features".
  • Store the calculated result in metric history and provide a warning test criterion saying that is value should always be zero (because we don't want any uncommented feature).
  • Then you can recalculate the metrics in history easily, and when the warning test criterion is violated, you'll get warned.
Test procedure:
  • Open compiled project.
  • Go to the metric tool
  • Select Metric Evaluation panel.
  • Input domain selector, where you can select input domain. -> base library
  • Metric selector -> uncommented feature.
  • Run button: Run selected metric over input domain.
  • Stop button: Stop undergoing metric calculation.
  • Send to history button: Send calculated metric result to metric history.
  • Keep detailed result button: An option to indicate if detailed results are kept for basic metrics. If detailed results are kept, you'll see a list of code elements if any in Detailed Result panel after metric calculation.
  • Filter not visible items button: An option to indicate if invisible elements from input domain should be filtered out. for more information about invisible elements, see document of criterion is_visible.
  • Automatic go to result panel button: An option to indicate if Detailed Result panel is switched to automatically after metric calculation.
  • re-run again the metric from the history panel

You can also try to remove a comment from a feature to test the warning.

Initial Conditions:

Compiled Eiffel system.

Expected result:

working test case.

Test runs

IDDatePlatformResult
trr#2981 year 11 weeks agoWindows 32bitPassed