Difference between revisions of "Application Testing"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
 
(One intermediate revision by the same user not shown)
Line 11: Line 11:
You can use either of those mechanisms to:
You can use either of those mechanisms to:
:* '''Send an Email''' to test a template
:* '''Send an Email''' to test a template
:* '''Invoke a method''' in a [[Java Class]] to test your code
:* '''Invoke a method''' in a [[Java class]] to test your code
:* '''Execute a Rule Set''' to test your [[Rules]]
:* '''Execute a Rule Set''' to test your [[Rules]]
:* '''Start a Process''' to test [[Process]] behavior
:* '''Start a Process''' to test [[Process]] behavior
<noinclude>
[[Category:Design]]
</noinclude>

Latest revision as of 01:55, 20 March 2014

There are two basic testing mechanisms:

  • To test operations that occur when a record is created:
  1. Create an Event Rule
  2. In a running system, set up a condition that restricts the rule to your testing, for example to ensure that the rule is triggered only when some flag is set, or only when you are the person creating the record, using a Created By field.
  • To test operations that occur for an existing record:
  1. Open the object and create a macro that invokes a method.
  2. When viewing a record, select the macro from the list of Actions.

You can use either of those mechanisms to:

  • Send an Email to test a template
  • Invoke a method in a Java class to test your code
  • Execute a Rule Set to test your Rules
  • Start a Process to test Process behavior