Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Step-by-step guide

Creating Test Cases helps with support, and testing configuration changes quickly by driving JEMHC directly, without requiring an email to be sent.  There are several ways to create a Test Case:

Creating a Test Case

From scratch using the Test Case UI

Just click Create:

Then you will get an edit window for a basic text email, useful for simple content related tests.  Test Cases need to be associated with a Profile, against which they will run, so at least one profile will already be needed.  Remember that profiles can be duplicated by copying, so one can be setup for testing purposes.  The + icon in the lower left of the edit window will flip the editor into full screen mode:

Full Screen editor mode shown below, re-click to minimize.

After hitting Submit, it will be listed (see next)

From Incoming email

By default, and if not opted-out, JEMHC will retain recent inbound email, allowing you to create a Test Case from the message received, to diagnose processing issues.  From the Auditing > Inbound Messages screen, when retention is enabled, there is a Generate Test Case action:

You'll get a confirm:

And when OK is pressed, a further dialog gives option to open the Test Case editor:

Outgoing email?

Outbound mail isn't designed to be processed by JEMHC but it can be exported for review:

Running a Test Case

The Test Case can be run against the related profile by clicking the run icon:

After executing a Test Case, some results are shown, the below is letting us know that the TO: address on the email didn't match the Profiles catchemail address, and as the Profile was configured to Drop non-matches, that's what it did (albeit that dropping mail doesn't apply to Test Cases):

 

  • No labels