AgileApps Support Wiki

Difference between revisions of "Test Results"

From AgileApps Support Wiki
imported>Aeric
m (Text replace - 'Setup > Develop > ' to 'Designer > Logic > ')
 
imported>Aeric
 
(13 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.
<noinclude>__TOC__</noinclude>
<noinclude>__TOC__</noinclude>
==== Summary ====     
==== Summary ====     
:* '''Tested Class''' - The class that was tested.
{{:Test Results Contents}}
:* '''Total Tests''' - The total number of test methods that were executed.
:* '''Failed Tests''' - Tests that failed, either because an assert failed or because an exception occurred.
:* '''Successful Tests''' - 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.
:* '''Empty Tests''' - Tests that ran to completion without making any assertions.
:* '''Code Coverage %''' - The percentage of runnable code in the class that was executed during the test. Click the link to view a [[Code Coverage]] popup window that highlights the executed lines.
:* '''Total Time (ms)''' - The total amount of time that was taken to execute the tests, in milliseconds.
<!--
{{Note|The sum of "Successful Tests" and "Failed Tests".
--how are assertions counted?
--how are empty tests counted?}}
-->


==== Failed Methods ====
==== Failed Methods ====
This section shows the methods 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.
 
<noinclude>
==== 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.
 
==== Successful Methods ====
This section list the tests that succeeded, and shows how long they took to run.<!--
==== Debug Log ====
Messages generated by <tt>Functions.debug()</tt> statements in the test methods are displayed here.--><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

Retrieved from "https://agileappscloud.info/aawiki-src/index.php?title=Test_Results&oldid=13200"