Skip to main content
Version: 2.29

Cycle FAQs

What training is needed to use Cycle?​

Cycle University is a good place to begin learning the basics. Training is recommended, although not required, to begin creating Feature Files. You can access Cycle University within the Cycle platform by clicking Help > Cycle University.

What kind of testing can Cycle be used for?​

  • Systems validation
  • Regression testing
  • Load/volume testing
  • Upgrade testing
  • Development unit testing

Does Cycle work well with hosted systems?​

Cycle emulates keyboard and mouse input that a normal user would use. Therefore, Cycle works on both hosted and non-hosted systems with the appropriate access.

How much time is required to write a test using Cycle?​

It depends on the number of Steps and the level of complexity within the test Scenario. A typical test Scenario takes about 4-8 hours of setup time. Below are examples of time for creating a Feature File.

Feature FileEst. time
Open terminal and move Load Number to allocated position1 hour
Create trailer, receive, dispatch8 hours
Create shipping trailer, allocate, pick, load, close, dispatch14 hours

Other than software testing, what else can Cycle be used for?​

Cycle can be used for workflow processes such as sending automated emails and running scheduled reports. In addition, Cycle has a Step Delay used to slow down Feature File execution so that Features can be run for training purposes.

Can Cycle help with volume/load testing?​

Yes. Cycle can emulate one or many users, which allows load testing for terminal devices from one PC.

What are some examples of time savings that Cycle provides?​

Below are examples of time savings for scripts run by a Super User compared to the automated Cycle run times:

Test 1: Create trailer, receive, dispatch

  • Super User: 3 minutes 11 seconds, 10 minutes data clean and set-up
  • Cycle: 2 minutes 15 seconds

Test 2: Open terminal and move lodnum to allocated position

  • Super User: 1 minute 16 seconds (no data setup needed)
  • Cycle: 50 seconds

Test 3: Create shipping trailer, allocate, pick, load, close, dispatch

  • Super User: 8 minutes and 12 seconds, 10 minutes data clean and set-up
  • Cycle: 3 minutes 10 seconds

Can you tell which tests pass or fail?​

Yes. Cycle shows each Step's result within the Test Output pane of the Cycle Desktop IDE and produces reports so you can review testing results. The following FAQ shows an example of the information provided in reporting.

What kind of reporting does Cycle provide?​

Cycle provides options for reporting to HTML or web reports, CSV reports, email summary reports, or directly to a data store.

Does Cycle require a license?​

Yes. Executing tests in Cycle requires users to have a valid license.

What type of customer service is provided for Cycle?​

Cycle Labs' maintenance and support for Cycle includes:

  • Standard documentation
  • User manual
  • Upgrades
  • Feature File templates
  • Remote/telephone support
  • Access to Cycle User Portal and Help Center
  • Access to Cycle University

Creating a user account to log in to Cycle​

Every Cycle customer has one administrator created upon purchase of licenses. That user is responsible for creating users via the User Portal. After the administrator creates an account for you, you receive an email prompting you to reset your password.

Requesting a floating strict license each work day​

No. Cycle automatically requests a license upon launching the application and authenticating a user. In addition, Cycle requests a license before executing a Feature File. Therefore, if you leave Cycle open over an extended period of time during which your license expires, you should not have to close Cycle to gain a new license.

Relinquishing a floating strict license at the end of the day​

No. Closing Cycle relinquishes your license automatically.

Logging in without checking out a license​

Being able to log into the Cycle client is not the same as having a license. Licenses are assigned to users. You can log into the client because you have a valid user account, but you can still run into errors when checking out a license for a variety of reasons. Visit Error Messages for more detail.

Cycle is automatically signing into a previous account​

After signing in successfully to Cycle, the client stores an API key to bypass the login on future launches. If someone else logged into the same Windows user and still has a valid account, the API key associated with that device can still be valid. That bypasses the sign-in process. To fix this, log out by going to Help > Logout in the top menu.

Using a node-locked license across PC user accounts​

Cycle licenses are stored on a per-PC-user basis. Two different user accounts on the same machine each need their own Cycle license.

Transferring a Cycle license between machines​

The API key that is generated for the respective Cycle license uses a unique hardware ID. Changing machines or running a copy of a VM results in a new hardware ID and requires a new API key.