June 2024

Enhancements

Create JavaScript to Validate items in Add to cart page

We are excited to introduce a new enhancement to GoTestPro: a JavaScript validation solution for the Add to Cart page. This feature ensures that all items added to the cart meet the necessary criteria, enhancing the user experience and preventing errors during the checkout process.

Key Features:

• Item Availability Check: The script verifies that the selected items are available in stock before allowing them to be added to the cart.

• Quantity Limits: Ensures that the quantity of items added does not exceed predefined limits, adhering to business rules and inventory constraints.

• Business Rule Validation: Validates other relevant business rules specific to the items being added, such as eligibility for discounts or special conditions.

• Seamless Integration: Integrates seamlessly with the existing cart functionality, providing real-time feedback to users.

Benefits:

• Error Prevention: Reduces the likelihood of encountering issues during the checkout process by validating items upfront.

• Enhanced User Experience: Provides immediate feedback to users, ensuring a smoother and more efficient shopping experience.

• Business Rule Compliance: Ensures that all items added to the cart comply with business rules and inventory policies, maintaining operational standards.

• Improved Efficiency: Streamlines the checkout process by catching potential issues early, reducing the need for manual interventions and corrections.

How to Use:

1. Adding Items to Cart:

   • When a user selects an item and attempts to add it to the cart, the JavaScript validation script will automatically execute.

   • The script will check for item availability, quantity limits, and other business rules.

   • If the item meets all criteria, it will be added to the cart. If not, an appropriate error message will be displayed, guiding the user on how to proceed.

2. Real-Time Feedback:

   • Users receive real-time validation feedback directly on the Add to Cart page, allowing them to make necessary adjustments before proceeding to checkout.

3. Handling Validation Errors:

   • If any validation errors occur, clear and informative messages will be displayed, indicating the specific issue and suggesting corrective actions.

Use Case:

• A user wants to add multiple items to their cart during an online shopping session. The JavaScript validation script checks each item for availability and quantity limits, ensuring that only eligible items are added. This prevents the user from encountering issues later in the checkout process and enhances their overall shopping experience.

Docker for On-Premises Installation of GoTestPro Web Application

We are pleased to announce a significant enhancement to GoTestPro (GTP) with the introduction of Docker support for on-premises installations. This enhancement aims to streamline the deployment and management of the GTP web application by containerizing its key components.

Key Components:

• Spring Boot Java Application: The core backend application providing business logic and API services.

• Angular Web Application: The frontend interface for users to interact with GoTestPro.

• MySQL Database: The database system for storing application data.

• Selenium Test Grid Setup: The infrastructure for running automated Selenium tests.

• Disabled Non-Applicable Features: Configuration to disable features that are not relevant for on-premises setups.

Benefits:

• Efficient Deployment: Simplifies the installation and deployment process, reducing the time and effort required to set up GoTestPro on-premises.

• Enhanced Manageability: Docker containers provide a consistent environment, making it easier to manage, scale, and update individual components.

• Isolation and Security: Each component runs in its own container, providing isolation and improving security.

• Consistency Across Environments: Ensures that the application behaves consistently across different on-premises environments by eliminating differences in setup and configuration.

How to Use:

1. Setup Docker Environment:

   • Ensure Docker is installed and running on your on-premises server.

   • Download the Docker Compose file provided by GoTestPro.

2. Deploy GoTestPro Containers:

   • Use Docker Compose to deploy the containers for the Spring Boot application, Angular application, MySQL database, and Selenium Test Grid.

   • Run the command docker-compose up to start all containers.

3. Configuration:

   • Access the configuration files to adjust settings specific to your on-premises environment.

   • Ensure that features not applicable to on-prem installations are disabled as per the provided configuration guidelines.

4. Monitor and Manage:

   • Use Docker tools and dashboards to monitor the health and performance of each container.

   • Manage updates and scaling operations seamlessly using Docker commands and configurations.

Bugs and Issues

API Request Variable Update Issue

There is an issue with API request variable updates in GoTestPro when executing tests in the cloud. The value of the extracted variable from the API request is not updating correctly during test execution.

Description:

When running tests in the cloud, variables extracted from API requests are not updating their values as expected. This leads to inaccurate test results and hampers the testing process, as subsequent steps relying on the updated variable values may fail or produce incorrect outcomes.

Steps to Reproduce:

1. Create a test scenario that includes an API request with a variable extraction step.

2. Execute the test scenario in the cloud environment.

3. Observe the value of the extracted variable during and after the API request.

4. Verify if the variable's value is updated correctly and propagated to subsequent test steps.

Expected Result:

The value of the API-extracted variable should update correctly during cloud test execution and be available for subsequent test steps.

Actual Result:

The value of the API-extracted variable is not updating properly during cloud test execution, leading to potential test failures and incorrect results.

Actions Hardcoded as 'Click' in Edit Mode

In Edit mode, all actions are incorrectly hardcoded as 'Click', preventing users from specifying and modifying different action types needed for their scenarios.

Description:

When users enter Edit mode to modify the actions of a test scenario, they find that all actions are hardcoded as 'Click'. This issue restricts users from accurately editing and specifying the necessary action types such as 'Input', 'Select', 'Hover', etc., which are essential for creating comprehensive and precise test scenarios.

Steps to Reproduce:

1. Create or open an existing test scenario.

2. Enter Edit mode to modify the scenario actions.

3. Attempt to change the action type for any step in the scenario.

4. Observe that all actions are preset as 'Click' and cannot be changed to other action types.

Expected Result:

Users should be able to modify and specify different action types (e.g., 'Input', 'Select', 'Hover') for each step in their test scenarios when in Edit mode.

Actual Result:

All actions are hardcoded as 'Click', preventing users from changing the action types and accurately editing their test scenarios.

Unable to Create New API Variable

Users are unable to create new API variables from the response payload. After making an API request and saving the response, attempting to add a variable by right-clicking results in the page continually loading without completing the action.

Description:

When users perform an API request and save the response, they should be able to create new variables from the response payload by right-clicking and selecting the appropriate option. However, upon attempting to do so, the page becomes stuck in a loading state and does not allow the user to successfully create the variable. This issue prevents users from utilizing dynamic data extracted from API responses in their tests.

Steps to Reproduce:

1. Make an API request and save the response.

2. Right-click on the response payload to add a new variable.

3. Observe that the page keeps loading indefinitely, preventing the creation of the variable.

Expected Result:

Users should be able to right-click on the response payload, select the option to create a new variable, and have the variable created successfully without any loading issues.

Actual Result:

The page keeps loading indefinitely when attempting to add a new variable from the API response payload, preventing the creation of the variable.

Open

Open