License Code
Last updated
Was this helpful?
Last updated
Was this helpful?
<dependency>
<groupId>in.precissiontestautomaton</groupId>
<artifactId>scriptless-automation</artifactId>
<version>1.4.1</version>
</dependency>
<dependency>
<groupId>in.precissiontestautomaton</groupId>
<artifactId>scriptless-automation</artifactId>
<version>1.4.2</version>
</dependency>
New Features:
Enhanced Scroll Action Handling: Introduced the capability to execute scroll actions without specifying a wait condition. This improvement allows for more flexible interaction with web elements, particularly in scenarios where waiting for a specific state isn't necessary. Users can now specify "NONE" as the wait parameter to immediately proceed with scroll actions, enhancing test script efficiency and adaptability.
Bug Fixes:
Enhanced Test Case Execution Through Configuration: Addressed an issue where executing multiple test cases via configuration settings led to inconsistent behaviors. This fix ensures a smoother, more reliable process for running batches of tests, improving overall test management and execution reliability.
Parallel Execution Report Naming Conflict Resolved: Solved a critical issue where reports generated from parallel test executions received identical names, leading to confusion and data loss. With this fix, each report generated from parallel executions is now uniquely named, ensuring clarity and traceability of test results.
Configurable Screenshot Capture on Test Pass/Fail: Implemented a new switch option to configure screenshot capturing behavior upon test step completion. With this feature, users have the flexibility to capture screenshots for successful test steps when the switch is enabled. Conversely, when the switch is off, screenshots are captured for failed test steps only. This enhancement provides better control over test documentation and aids in efficient debugging and reporting by focusing on the required evidence based on test outcomes.
Improvements:
Optimization by Removing Chrome DevTools Feature: To boost the performance of our automation suite, we have removed the integration with Chrome DevTools. This change significantly reduces the overhead caused by DevTools communication, leading to faster test execution times and overall enhanced automation performance. This optimization is part of our ongoing efforts to streamline testing processes and improve efficiency.
<dependency>
<groupId>in.precissiontestautomaton</groupId>
<artifactId>scriptless-automation</artifactId>
<version>1.4.3</version>
</dependency>
Dynamic Data Validation Across Environments: We've added a powerful feature that allows the tool to read and validate data dynamically, depending on the environment it's operating in. This ensures that our automation tool can adapt its testing strategies based on development, testing, or production environments, offering more accurate and environment-specific test outcomes. This feature is especially beneficial for teams working in complex, multi-environment setups and aims to enhance testing accuracy and efficiency.
Environment Configuration: The TestNgConfiguration.properties
file specifies the active testing environment through the ENV
variable, such as qa
or sandbox
.
Dynamic Data Selection: Based on the ENV
setting, the tool dynamically selects a corresponding directory within the test_data
folder. Each directory contains property files with environment-specific data.
Property Access Syntax: Data within these files is accessed using a syntax like $text.title
, where $
signifies a dynamic string, text
is the property file's name, and title
is the key whose value is fetched.
Consistent File Naming: For the syntax to work across different environments, it's mandatory to maintain consistent property file naming within all directories.
Application to Test Fields: This dynamic data referencing mechanism is applicable to fields such as SEND_KEYS
and VALIDATION
in the automation scripts, allowing for flexible and environment-specific testing.
This process enables the automation tool to validate and interact with data that is specific to the environment in which it is running, thus enhancing test accuracy and efficiency.
Enhanced Test Management with DISABLE_TEST_RAIL_IDS
: Responding to feedback for greater test execution control, we have introduced the ability to selectively disable test cases using the DISABLE_TEST_RAIL_IDS
environment variable. By specifying a list of TestRail IDs, users can now easily exclude non-relevant or problematic tests from their execution cycle. This update is designed to streamline test management and improve focus on critical test cases.
New Improvements:
N/A
<dependency>
<groupId>in.precissiontestautomaton</groupId>
<artifactId>scriptless-automation</artifactId>
<version>1.4.4</version>
</dependency>
CSS Property Validation Enhancement: We've added a feature for validating CSS property types, enabling users to ensure UI components match expected CSS values accurately. This feature uses a syntax template that users can adapt to their specific validation requirements:
Syntax Template:
PAGE_NAME,WAIT_TYPE,SCROLL_TYPE,ELEMENT_NAME,ACTIONS,SEND_KEYS,VALIDATION,VALIDATION_TYPE
VALIDATION_TYPE
should be set to CSS_PROPERTY
.
VALIDATION
should follow the template "cssExpected | CssPropertyName"
.
Example: To validate the font-family of a page title in SwagLabs, the syntax would be:
SwagLabs,NONE,NONE,pageTitle,NONE,NONE,"""DM Mono"", ""sans-serif""|font-family",CSS_PROPERTY
This feature allows for the comparison of the actual CSS value from the web against the expected CSS value (cssExpected
), based on the specified CSS property name (CssPropertyName
).
Reports:
Group-based Test Case Execution: To improve test case execution flexibility, we now support executing test cases based on group names (e.g., sanity, regression). This is facilitated by naming CSV files following the template Testcase_groupName.csv
and specifying the required group name in testManagementConfiguration.properties
.
Key Conditions:
TestManagementConfig.TEST_TRAIL_IDS
must be set to more than one test case or ALL
.
To execute all test case groups, set GROUPS=ALL
in testManagementConfiguration.properties
.
This release introduces tools for more precise UI testing and more efficient test case organisation and execution. The syntax templates provided are designed to be flexible, allowing users to tailor their testing approach to meet specific requirements.
<dependency>
<groupId>in.precissiontestautomaton</groupId>
<artifactId>scriptless-automation</artifactId>
<version>1.5.0</version>
</dependency>
Zephyr Test Management: We've extended our test management toolkit by integrating with Zephyr. This addition allows for seamless synchronization of test cases and results within Zephyr, streamlining the workflow for teams that utilize this popular test management solution.
BrowserConfiguration: The configuration files have been restructured to create a dedicated directory for browser settings, starting with support for Chrome and laying the groundwork for additional browsers in future releases.
CommunicationConfiguration: Configuration for communication tools, like Slack, has been moved to its own directory, which will be expanded with more options in the future.
MailConfiguration: Email configurations, currently supporting Gmail, now have a separate directory, anticipating the inclusion of more email services going forward.
ReportConfiguration: Reporting tools such as ExtentReport now reside in a new directory, with plans to support more reporting tools soon.
TestManagement Configuration: The existing integration with TestRail and Zephyr has been compartmentalized into its own directory, with intentions to extend support to additional test management tools.
This new directory structure for configuration not only simplifies the setup process for users but also improves maintainability and scalability of the configurations.
ATTRIBUTE_CONTAINS Validation: We've added a new validation type, ATTRIBUTE_CONTAINS
, allowing you to check if an element's attribute contains a specific value, thereby broadening the scope of your automated test validations.
PAGE_NAME,WAIT_TYPE,SCROLL_TYPE,ELEMENT_NAME,ACTIONS,SEND_KEYS,VALIDATION,VALIDATION_TYPE
SwagLabs,NONE,NONE,userName,NONE,class,form_input,ATTRIBUTE_CONTAINS
UI Element Highlighting In Report
In line with providing a more intuitive and informative reporting experience, elements on the web page are now automatically highlighted when screenshots are captured. This visual aid accentuates the focus area in screenshots, making it clearer what each test step validates.
<dependency>
<groupId>in.precissiontestautomaton</groupId>
<artifactId>scriptless-automation</artifactId>
<version>1.5.1</version>
</dependency>
Testiny Test Management: We've extended our test management toolkit by integrating with Testiny. This addition allows for seamless synchronization of test cases and results within Testiny, streamlining the workflow for teams that utilize this popular test management solution.
<dependency>
<groupId>in.precissiontestautomaton</groupId>
<artifactId>scriptless-automation</artifactId>
<version>1.5.2</version>
</dependency>
New ActionType - SAVE_VALUE: Save the text from the element input value into global variables efficiently with the new ActionType feature. The saved text can be used as input for further steps or for validations.
<dependency>
<groupId>in.precissiontestautomaton</groupId>
<artifactId>scriptless-automation</artifactId>
<version>1.5.3</version>
</dependency>
New ValidationType - PAGE_COMPARISON:Validate the screenshot taken from the driver against the expected screenshot to ensure accuracy with the new PAGE_COMPARISON feature.
New ValidationType - IS_NOT_DISPLAY:Ensure that an element is not displayed on the page with the IS_NOT_DISPLAY validation type.
New ValidationType - IS_ELEMENT_PRESENT:Verify the presence of an element in the DOM with the IS_ELEMENT_PRESENT validation type.
New ValidationType - IS_ELEMENT_NOT_PRESENT:Ensure that an element is not present in the DOM with the IS_ELEMENT_NOT_PRESENT validation type.
New ValidationType - NOT_EQUALS: Ensure that an element text is not equal to expected text.