If the activity requires extensive setup and is more appropriately tested in context rather than through unit testing, you can trigger the Tracer to start only when the activity is reached.
To test an activity in the context of other activities and rules that produce the needed initial conditions, complete the following actions:
Open the activity.
Select Actions > Trace. The Tracer tool starts.
To avoid using more memory than needed while tracing, click Settings in the Tracer window and ensure that only the ruleset containing the activity is selected in the Rulesets To Trace section.
Begin the other processing that eventually calls the activity in your own requestor session. Tracer output begins when the activity starts.