AgileApps Support Wiki Pre Release

Difference between revisions of "Test Results"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
<noinclude>'''Designer > Logic > Classes > {class} > [Run Tests]'''</noinclude>
<noinclude>'''[[File:GearIcon.png]] > Customization > Developer Resources > Classes > {class} > [Run Tests]'''</noinclude>


This page shows the results of running the tests defined in a class.
This page shows the results of running the tests defined in a class.
Line 8: Line 8:
==== Failed Methods ====
==== Failed Methods ====
This section shows the tests that failed, either because an exception occurred or because an assertion statement turned out to be false. The error message is displayed in either case. If there was an exception, a stack trace is shown, as well.
This section shows the tests that failed, either because an exception occurred or because an assertion statement turned out to be false. The error message is displayed in either case. If there was an exception, a stack trace is shown, as well.
==== Success Methods ====
This section list the tests that succeeded, and shows how long they took to run.
==== Code Coverage ====
Shows the percentage of runnable code in each method that was executed during the test. Click the link to view a [[Code Coverage]] popup window that highlights the executed lines. (When done viewing coverage, close the popup to continue working in the platform.)
<noinclude>
<noinclude>
====Learn More====  
====Learn More====  
:* [[Unit Test Framework]]
:* [[Unit Test Framework]]
</noinclude>
</noinclude>

Latest revision as of 21:11, 29 July 2014

GearIcon.png > Customization > Developer Resources > Classes > {class} > [Run Tests]

This page shows the results of running the tests defined in a class.

Summary

  • Tested Class - The class that was tested.
  • Tests Run - The total number of test methods that were executed.
  • Test Failures - Tests that failed, either because an assertion failed or because an exception occurred.
  • Tests Succeeded - A count of the number of assertions that succeeded. If a single test method makes 2 assertions, and each succeeds, it counts as 2 successful tests.
  • Total Time (ms) - The total amount of time that was taken to execute the tests, in milliseconds.

Notepad.png

Note: Tests that run to completion without making any assertions are not counted.

Failed Methods

This section shows the tests that failed, either because an exception occurred or because an assertion statement turned out to be false. The error message is displayed in either case. If there was an exception, a stack trace is shown, as well.

Learn More