Cycle 2 New API Testing, reflects the focus on improving usability, flexibility, and efficiency in API integration and testing processes.
Simplify Steps: The new API testing aims to reduce the number of steps needed to interact with an API compared to the old approach.
Looser Coupling: The new approach promotes loose coupling between features and API calls. This means that the feature doesn't need to have an intimate knowledge of how the API works, offering a flatter learning curve and making it more user-friendly.
Variable Flexibility: Users can use whatever variables they want within the API, making it more flexible and eliminating the need for variable names to match the keys for headers and parameters.
Autocomplete: The API calls feature offers autocomplete.
User Skill Level: The new API screen is more suited to users with some technical knowledge, while the feature itself can target less technical users.
Future Enhancements: Considerations for future enhancements include displaying required variables in the step and further improving debugging features. There is a desire to enhance debugging capabilities, such as a "test" button to validate API calls and the ability to view API call output directly within the API screen.
Specific bug fixes & minor enhancements
We've made significant improvements to the behavior of lists in our automation tool. Any modifications to a list will now automatically reset the iterator used in the "I assign next element in list to variable" step. This step allows you to access elements in a list by their position, making it easier to work with specific elements within a list. This ensures a more seamless experience when working with lists.
We're excited to introduce a new step for Java app automation: "I enter <TEXT> in last object <cssSelector>:<OBJECT_IDENTIFIER> in java app within <NUMBER> seconds." This step enables you to interact with Java applications more effectively by entering text into specific objects within a Java app with a defined time constraint.
We've added two new steps to streamline interactions with Chrome authentication:
"I open Chrome web browser using basic authentication with saved credentials": This step allows you to open a Chrome web browser with saved authentication credentials, simplifying access to secured websites.
"I open Chrome web browser using basic authentication with username <user> and password <pass>": This step enables you to open a Chrome browser with specified username and password for basic authentication.
The "I Replace Variables in XML" stages have undergone major modifications to guarantee that namespace prefixes are now represented correctly in the final XML. This enhancement guarantees better compatibility and accuracy when working with XML documents within our platform. You can now seamlessly replace variables in XML while maintaining the integrity of namespace prefixes.
In response to user feedback, we've fine-tuned the behavior of our editor autosuggest feature. Autosuggest is now triggered in a more unobtrusive manner, providing a smoother and less distracting experience while working in the editor. This improvement allows you to focus on your tasks without unnecessary interruptions, enhancing your overall productivity.
Headless Edge is now supported in our automation tool. You can now execute your automation scripts in a headless Edge browser environment for enhanced performance and resource optimization.
"I assign moca status to variable": This step allows you to capture and store the MOCA (Mobile Commerce Application) status in a variable for further processing.
"I assign moca message to variable": This step enables you to extract and save MOCA messages into a variable for later use.
"I copy output directory path to variable": Use this step to conveniently copy the path of the output directory to a variable, facilitating file and directory management in your automation workflows.
I assign files in project directory "<local_file_path>" matching regex "<regex>" to variable "<variable_name>"
I assign "<suffix>" environemnt file in project directory "<local_file_path>" to variable "<variable_name>"
I assign "<string>" to variable "<variable_name>" after being UPPER|LOWER cased
Tools
menu to help identify Java App elements.within
logic for Java App driver steps to use Cycle's within logic instead of the Marathon Driver's.I close java app
Step.I do not see element in web
for verification...In App
key press Steps.I assign USERNAME from credentials...to variable...
$
variables rather than @@
variables, read more.TType
.File > Recent > Projects
to easily reopen recent projects.--token
argument in Cycle CLI to --user
to specify user profile to use for execution.POST
, GET
, PUT
, PATCH
, and DELETE
.Edit > Preferences
to switch to Dark mode.I clear all text in element "<ELEMENT_ID>" in web browser
Test Connection
button in Data Store Connection settings to also verify whether the Data Store schema is using the latest version.I execute MOCA dataset "<DATASET_DIRECTORY_PATH>"
cannot find the file specified.I SHIFT click element...
and I CTRL click element...
.Application ID
for MOCA connections to aid in limiting Cycle's production access when appropriate.WH_ID
and CLIENT_ID
to some Steps that were missing those parameters and needed them.Create Database Tables
under Data Store Connection to Create/Update Database Tables
to reflect extended functionality of updating the Data Store schema.Given I press <MINIMIZE|MAXIMIZE|CLOSE|RESTORE|FIND|SAVE|NEW|COPY|CUT|PASTE> Shortcut
to remove the full list of pipe-separated values from the Step itself and add them as examples in the Step Assistant.I save screenshot
and I save screenshot as "<FILE_PATH>"
to include screenshot images in web reports and Data Store whether or not the “save matched images” setting is turned on.Project settings > Advanced settings
for SSL validation through a Truststore file.Skip SSL Validation
was turned on.filepassword
and a userpassword
.If I see image...
Step.I see...in terminal
Steps.I maximize Cycle
and I minimize Cycle
.I open new tab in web browser
Step in Internet Explorer.I press keys...in terminal
Step failing when it should not.I execute MOCA dataset…
Step stalling.I prompt…
Step hanging on execution.I open new tab in web browser
Step causing an error in Chrome. For IE, I press keys "CTRL+T"
still preferable.I navigate to "<URL>" in web browser
.lastMocaCommand
that was available in previous Cycle versions.I hold down keys <KEY_OR_KEY_COMBINATION>
and I release keys <KEY_OR_KEY_COMBINATION>
.I click "Image:<IMAGE_FILE_PATH>" with correlation <NUMBER> within <NUMBER> seconds
.I do not see...
image Steps so they are less confusing.I see error message "<ERROR_MESSAGE_TEXT>" in terminal
.identifier <LOAD|SUBLOAD|DETAIL|LOCATION> "<TEXT>" contains <NUMBER> units
and identifier <LOAD|SUBLOAD|DETAIL|TRAILER> "<TEXT>" is in location "<TEXT>"
.I start tracing to trace file "<PATH_TO_FILE>"
.I assign next value from sequence "<SEQUENCE>" to "<VARIABLE_NAME>"
and I get the next value for sequence "<TEXT>" as "<TEXT>"
.I execute SQL script "<SQL_FILE_PATH>"
, I clean out data from SQL dataset "<PATH_TO_CLEANUP>"
, and I execute cleanup script for SQL dataset "<DATASET_DIRECTORY_PATH>"
.RF line contains...
Steps.File > Recent
menu include files created, saved, and closed within the current Cycle session.