
Developed a complete no-code automation solution using BrowserStack Low Code Automation (LCA) for a SAAS web application. The framework covered the entire QA pipeline — from test creation to execution, validation, and reporting — entirely through a visual interface, with no scripting required.
Accessed through the three-dot menu, BrowserStack LCA allowed powerful test actions such as:
Successfully implemented a robust, modular, AI-assisted, and visually verifiable automation framework using BrowserStack LCA. The entire solution:

This is the main test automation dashboard in BrowserStack Low Code Automation (LCA), under the Default Project - LCA workspace. All test modules built for the SAAS platform are organized and listed here for quick execution and monitoring.
What it shows:
Purpose:
To centralize and run QA automation without writing code manually — using AI-based, visual low-code workflows.

This screen represents the automation flow configuration for the SAAS College login and dashboard validation test using BrowserStack’s Low Code Automation (LCA) framework. It's part of a structured suite under the SAAS → Automation → Dashboard path.
What it shows:
Purpose: To ensure automated login flow verification for the SAAS college product and validate the user landing dashboard. Built for fast regression runs with no-code interaction using BrowserStack LCA.

This interface shows the test authoring view in BrowserStack Low Code Automation (LCA), where individual test flows are recorded and configured for SAAS application QA.
What it shows:
Purpose:
To visually build test flows with no scripting. This screen allows rapid QA test development for login flows, validations, and interaction coverage — designed for non-technical users or rapid prototyping in agile teams.

This screen highlights the Visual Validation capability in BrowserStack Low Code Automation, used during test creation for the SAAS College dashboard flow.
What it shows:
Purpose:
To enhance UI regression accuracy by capturing the visual state of the application (beyond DOM text), ensuring robust validation of layout-sensitive elements in the SAAS platform.

This view showcases the Text Validation feature being used while recording a test for the SAAS College platform in BrowserStack Low Code Automation (LCA).
What it shows:
Difference from Visual Validation:
Whereas Visual Validation checks layout and rendered visuals, Text Validation ensures the correct content is rendered and matches exactly — crucial for verifying user-facing text and copy.
Purpose:
To strengthen content accuracy validation in automated flows. This ensures that SAAS dashboard labels, messages, and status indicators are displayed as expected after actions like login.

This interface highlights the use of AI-powered validation during test authoring for the SAAS College test flow inside BrowserStack Low Code Automation.
What it shows:
Purpose:
To use natural language instructions for smart validations in test flows. This is especially useful in cases where traditional visual or text validation is limiting — for example, sorting, column comparisons, numerical thresholds, etc.

This screen illustrates the use of AI-driven action commands within the BrowserStack Low Code Automation tool, as part of the SAAS College login-to-dashboard test flow.
What it shows:
Purpose:
To allow non-technical testers or fast automation builders to express interaction logic using plain English. It eliminates the need for traditional scripting or element targeting logic and is ideal for dynamic UIs like date pickers, dropdowns, and filters.

This interface displays the extended capabilities menu available during test creation in BrowserStack Low Code Automation (LCA). These options allow test authors to build advanced, dynamic, and end-to-end automated test flows — extending well beyond basic UI interactions.
What it shows:
Upon clicking the three-dot (⋮) menu during test creation, the following options are revealed:
Each of these enhances flexibility, supports real-world test cases (e.g., login verification emails, conditional dashboards), and allows deeper end-to-end QA automation.
Purpose: To build enterprise-grade automation flows in a low-code environment — without compromising on power or custom logic. These features allow seamless integration between frontend, backend, and data validation layers in a single test case.

This view demonstrates the use of the Create Module feature in BrowserStack Low Code Automation (LCA), allowing users to convert frequently used steps into reusable blocks.
What it shows:
Purpose:
To enable reusability and standardization in test building. Modules act like subroutines, ensuring consistent and efficient test coverage across workflows that share a common sequence.

This screenshot also showcases the Create Loop feature in LCA, designed to repeat a selected group of steps based on iteration logic.
What it shows:
Purpose:
To support repetitive validation or interaction logic in automated tests. This removes the need to duplicate steps and allows efficient execution over large or variable datasets.

This interface shows the step deletion confirmation dialog in BrowserStack Low Code Automation (LCA), used when the user wants to remove one or more recorded steps from a test case.
What it shows:
Purpose:
To allow safe removal of redundant, incorrect, or outdated steps in an ongoing test. The confirmation ensures intentional deletion, maintaining test integrity during iterations.

This screen highlights the use of the Import Module feature in BrowserStack Low Code Automation (LCA), allowing test creators to reuse previously built modules across multiple test cases for better maintainability and speed.
What it shows:
Modules are designed to encapsulate common actions (e.g., login, page setup, cleanup) and are injected as single units, making test cases easier to manage and update.
Purpose:
To support efficient test development by enabling reuse of standardized, validated modules. This helps maintain consistency across tests, reduces duplication, and accelerates test creation in large QA suites.

This screen shows the main dashboard under the Test Suites tab inside BrowserStack LCA. It lists all created test suites, offering visibility and quick control over suite configuration, scheduling, and execution.
What it shows:
Purpose:
To provide a central place for managing, running, and maintaining automated test groups efficiently.

This screen initiates the creation of a new test suite in LCA. Testers define the suite name, platform (desktop/mobile), and select which browsers to run the suite on.
What it shows:
Purpose:
To define the suite’s identity and base execution environment before adding test cases.

This modal allows users to browse and select existing tests to be bundled into the suite.
What it shows:
Purpose:
To enable efficient test case selection for bundling related tests under one suite.

Once tests are selected, this view shows all selected tests with drag-and-drop support to reorder their execution sequence.
What it shows:
Purpose:
To finalize and order test executions before moving to suite-level configurations.

This screen provides test suite–level configurations after test selection, covering scheduling, environment setup, rerun logic, and CI tool triggers.
What it shows:
Purpose:
To fine-tune how and where the test suite will run — especially for production-ready pipelines.

This is the final overview of the created test suite. It lists all tests added, shows who last updated each, and allows for immediate execution or editing.
What it shows:
Purpose:
To give a clean and actionable summary view for the full test suite post-creation — ready to run or maintain.

This screen captures what happens immediately after clicking Run on a test suite. BrowserStack LCA initiates a Build — the automated execution of all tests grouped in the suite — and queues it for execution.
What it shows:
Purpose:
To launch batch execution of all selected tests under the suite — marking the start of test run processing across configured browsers. This allows tracking, live feedback, and future result review.

This screen shows the Builds tab, where BrowserStack LCA displays all active or completed test suite executions. Each build represents a triggered run of a test suite, with live status and control options.
What it shows:
Purpose:
To track the execution status of test suites in real time. The build view provides central access to ongoing or historical results, including logs, durations, and outcomes.

This screen displays the final status of all test cases inside the triggered test suite build (SAAS Automation Test-1). Each test’s result, duration, and failure breakdown is visible — allowing immediate triage and rerun if needed.
What it shows:
Purpose:
To give QA teams a clear, step-by-step breakdown of test suite execution results, identify failures fast, and rerun impacted flows without re-triggering everything manually.

This screen displays the detailed view of a single test within the test suite execution (build), showing each recorded step, its result, duration, and a video playback of the test run. It's designed to give full traceability into what happened during execution — step by step.
What it shows:
Purpose:
To inspect exact behaviors, failures, and UI state during automated runs — whether to debug failures, verify correctness, or confirm test environment conditions. The video makes this audit-grade and easy for non-technical reviewers too.

This view shows a failed test step with detailed debug context. The execution of the SAAS → Automation → Profile test failed at step 13 during a heading validation, and the screen provides video playback, logs, retry info, and exact mismatch details.
What it shows:
Purpose:
To give exact, reproducible visibility into why a test failed. This eliminates guesswork by showing what the UI actually rendered vs what was expected — making failures traceable, understandable, and actionable.

This screen captures a mismatch between visual playback and test execution status. The test case (SAAS → Automation → Brand Jobs) passed all steps, but the recorded video playback shows a blank browser window stuck on a data:, URL, raising questions about test reliability or network issues.
What it shows:
Root Cause Indicators:
Purpose:
This highlights the importance of validating not just test step pass/fail in the result pane but also cross-verifying with visual playback and logs. It's a key QA practice to detect false positives or shallow test coverage.

This document contains module-wise test case design for the SAAS platform, created using BrowserStack's Low Code Automation (LCA). Each test case is structured to verify key functionalities like UI elements, navigation flows, form actions, and data integrity across multiple user roles (Admin, Student, Recruiter).

Bug Title: Profile Module Missing – Not Visible or Accessible from Navigation
Reported In: SAAS Automation Test Suite (via BrowserStack LCA)
Tool Used: Trello (Bug Tracking Board)
Issue Summary:
The Profile module is missing from the SAAS platform’s navigation menu for logged-in users. As a result, the automation test for the Profile section failed since the element was not found in the UI.
Steps to Reproduce:
Expected Result:
Profile should be visible and clickable in the menu
Copyright © 2025 Vrashank Dhar - All Rights Reserved.
We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.