A Campaign is a schedule of one or more Test Cases associated with a Plan that runs the
tests at the requested time with the requested number of calls using a specific number of
concurrent calls. An Account can have multiple Plans, meaning you can subscribe to multiple
Plans at the same time, like Pulse (quality assurance) or Replay (regression testing), and so
on. Each Plan can have multiple Campaigns associated with it and each Campaign can be
associated with multiple Test Cases.
From the main menu, click . A screen similar to the one below is displayed:
Edit the Campaign: When you click the Campaign Name link, it opens up the Edit Campaign screen. You can edit the Campaign.
To execute, abort or delete the Campaign, select the checkboxes next to the Campaign name, click Action and select the appropriate action.You can also click the appropriate button in the individual Campaign row to run, abort, or delete the Campaign.
If you click Run, the Campaign will be scheduled to run immediately. You can view its progress by refreshing the page.
If you want to stop a Campaign midway through its execution for any reason, click Abort. One example is when the IVR is unable to handle the load and has crashed.
Click Delete to delete a Campaign. When a Campaign is deleted, the results of that Campaign will still remain in the Cyara Database, to keep a record of how the Campaign performed. This allows you to still generate reports for deleted Campaigns, and these are available in the Reporting module. You cannot delete Campaigns that are running or queued.
Different Types of Test Campaigns
Campaigns are associated with the Cyara plans such as Velocity, Pulse, Cruncher or Virtual Agent plans. Plans must be active on your Account to run an associated Campaign.
Velocity Campaigns help automate the execution of functional and regression testing of IVR sytems. Each associated Test Case is executed once per data scenario. The greater the number of concurrent ports that are assigned to a Velocity Campaign, the less time it takes to complete the Campaign run.
Cruncher Campaigns test the system's stability to handle large call volumes. They are used for load and stress testing. Typically, Cruncher Campaigns use a large number of concurrent ports and only a few Test Cases. Test cases are executed based on time or number of calls and test case distribution.
Pulse Campaigns test the end-to-end availability and performance of a system. They can be run continuously or at scheduled intervals on live IVR systems to check the availability and performance of the system at any time. If any failures are detected, notifications are sent to the Pulse Dashboard, Cyara mobile app or email.
Premium Pulse Campaigns support synchronized Campaigns to test customer-to-agent scenarios.
The main differences between Cruncher and Pulse Campaigns are the number of concurrent ports used and the number of Test Cases executed.
Outbound Campaign does not make any calls, but instead receives calls from the IVR/dialer being tested and acts as a customer receiving a call.
Comments
0 comments
Please sign in to leave a comment.