FREQUENTLY ASKED QUESTIONS

CI/CD

Cycle was built to easily fit into your CI/CD workflow.

General Questions

Cycle is easy-to-use, meaning all business stakeholders—technical and non-technical—can understand, build, and align on tests. Using the built-in recording functionality in Cycle, business process experts of varying technical backgrounds can create complex and complete tests by simply recording desktop and terminal user actions.

Cycle supports testing via controls like keyboard and mouse input, ensuring tests are run exactly as users would execute them. This unique approach allows Cycle to interact with any enterprise software system you need to test. Additionally, powered by Selenium, Cycle supports programmatic web-based testing with over 100 built in Steps specifically designed for testing web-applications.  Cycle also supports built-in terminal emulation (Telnet/SSH), exactly how the user interacts with the terminal and allows for advanced dynamic testing. The terminal emulator in Cycle can emulate a single terminal emulator or a batch of terminal emulators from the same Cycle instance. Launching a batch of terminal emulators is useful for group testing.

  • System validation
  • Acceptance testing
  • Regression testing
  • Load/volume testing
  • System sizing validation
  • Unit testing
  • User training
  • SOP/detailed work instructions
  • Process documentation

We like to say that if a user can do it (and sometimes even if a user can’t), so can Cycle. So far, we’ve not run into a native, terminal, or web-based application that Cycle doesn’t support.  Please feel to contact us if you have compatibility questions.

A programming background is not needed to start working with Cycle, as it was designed for all types of users.  The built-in help functionality is very robust, with features like autosuggest that appear as a user types and “Step” guides that show detailed examples. You could be working on a GUI interaction test within minutes of installing Cycle. For those who prefer hands-on instruction, we have training packages available.

Cycle is available via a local install from the Cycle User Portal. The Cycle User Portal provides quick access to all your Cycle downloads, including the latest version, release notes and supporting documentation.

We strongly believe that tests are only as powerful as the data driving them. But, we also know that creating and using test data can be a real headache. With Cycle, there are a variety of ways to build and use test data, including reading from a database, text or CSV files, or direct on-screen user prompting.

Cycle can connect to Oracle, SQL Server, MySQL, or DB2 databases using JDBC (Java Database Connectivity). Once connected, SQL commands can be executed via Cycle Feature Files.

It is common for regression tests to be created to run against a known set of data. It is also common to run a regression test or set of tests many times. To support these types of tests, Cycle provides functionality to load datasets into a database using MOCA or JDBC connections. Cycle also provides functionality to clean up or remove data. Cleanup activity may occur before or after a test is executed.

To learn more about how Cycle manages data, click here.

Cycle’s built-in testing language is very high level, modular, and both concise and readable enough to double as documentation usable by both technical staff and “business” users alike. Inspired by Behavior-Driven and Domain-Specific Languages used by technical teams for more than a decade, Cycle tests are designed to be a communication medium between non-technical business users and their more technical IT counterparts. Constructing a test in Cycle feels more like describing a business process than building an automated test.

At this time, we do not offer multilingual support - Cycle is offered only in English (US).

Compatibility

Microsoft® Windows 7, 8, or 10, Microsoft® Windows Server®

Currently the latest publically-available versions of Chrome and Internet Explorer are supported. 

Cycle has extremely robust and powerful support for terminal and command-line based applications and can support regression and performance testing of those applications natively within Cycle. However, Cycle does not currently support the testing of other native mobile applications the applications can be ran in a web browser or have Windows desktop-based mobile simulation. We do have plans to focus on native mobile applications in the future, and if you’d like to discuss our plans, please reach out to us (info@cycleautomation.com). We would love to hear your thoughts on how Cycle should support native mobile applications.

Licensing

Pricing can vary depending on your business's needs and usage, so please send us an email at info@cycleautomation.com or fill out the Contact Us form and we'll be happy to provide you with pricing information specific to your situation.

Licenses are managed via the Cycle User Portal. Cycle administrators have the ability to add and remove users, while all users can view license availability and details.

Reporting

Cycle has the ability to generate HTML reports that show all activity that took place during a test’s execution. Report generation can be enabled or disabled in Preferences. Use the “Reporting settings” section of the Application Preferences screen to turn on report generation and set the output directory.

To view a report, open the HTML file in the report directory with the name of the executed file and the timestamp of the execution. The report will display statistics for all of the Feature Files that were executed.

Cycle can also send summary reports right to your inbox. Use the “Reporting settings” section of the Application Preferences screen to turn on “Send email summary” and set the necessary parameters to send the email.

An email summary report gives a high-level view of the status of the execution. The title of the email will be "Your Cycle Report - The Name of the File Executed - STATUS". The contents of the email provide information on how many steps passed and failed, as well as details on the environment of the test execution.