diff --git a/README.md b/README.md index 205c287fc..f0465e38e 100644 --- a/README.md +++ b/README.md @@ -1,36 +1,110 @@ -# [TestMu AI Documentation](https://testmu.ai/support/docs/) -Welcome to TestMu AI's documentation repository! Help us enhance our documentation by contributing—whether it's fixing a typo or adding new topics. We appreciate all contributions. +# TestMu AI (Formerly LambdaTest) Documentation -## Contributing Content -We recommend forking the repo, creating all content changes in branches, and submitting pull requests. We will work with you to get this content reviewed, tested, and merged for publishing. +

+ Made by TestMu AI +Docusaurus Community +

-## Building Locally -Docusaurus requires the following to build on locals: +## Getting Started -- [NodeJS](https://nodejs.org/en/download/) version recommended: `16.14.0` -- Verify the Node.js version by opening Command Prompt/Terminal and running `node -v` -- Download Git [here](https://git-scm.com/downloads) -- [VS Code Editor](https://code.visualstudio.com/download) +[TestMu AI](https://www.testmuai.com/) (Formerly LambdaTest) is the world's first full-stack AI Agentic Quality Engineering platform that empowers teams to test intelligently, smarter, and ship faster. Built for scale, it offers a full-stack testing cloud with 10K+ real devices and 3,000+ browsers. With AI-native test management, MCP servers, and agent-based automation, TestMu AI supports Selenium, Appium, Playwright, and all major frameworks. -To build on your local: +This repository powers TestMu AI documentations built with Docusaurus and React. Contributions are welcome, whether it is fixing a typo or adding a new topic. The docs team will review and ship your changes. -1. Clone the repo using Git or tools like GitHub Desktop. -2. In a terminal, change to the cloned repo folder. Run the install command: `npm install --legacy --peer-deps`. -3. To serve and review your content, use one of the following: - - Use start, hot reloads as you make changes: `npm start`. -4. To build locally and test your links, run `npm run build`. Any issues with broken links and images are listed according to file. Locate and update those issues, then run `npm serve` and start again to verify. +- [Sign up on TestMu AI](https://www.testmuai.com/register/) (Formerly LambdaTest). +- Browse the [TestMu AI Documentation](https://www.testmuai.com/support/docs/) for product guides and references. -Note: If the command doesn't work, try `npm i react-scripts@latest` followed by `npm start`. +### Prerequisites -The static files are generated in the build folder and run on your local machine at: http://localhost:3000/. To stop the build or served site, hit Ctrl + C to interrupt. You can enter new commands in terminal, rebuild, and restart. +- [Node.js](https://nodejs.org/en/download/) 18.0 or higher (verify with `node -v`) +- [Git](https://git-scm.com/downloads) +- A code editor such as [VS Code](https://code.visualstudio.com/download) -[TestMu AI Documentation](https://testmu.ai/support/docs/) was created using [Docusaurus 2](https://docusaurus.io/) with React +### Setup -## Publishing Content -- Clone the repository to your local machine -- Switch to the `stage` branch / you can create your desired branch as well. -- Now after completing your changes, raise the PR for the `stage` branch only and ask to the docs team to review and merge it for `stage`. -- Verify your changes on the stage domain. -- Now to deploy your changes to the PROD, provide all the PRs related to that feature to the docs team, they will merge it to PROD. +Clone the repo and install dependencies: -As pull requests are merged to the `main` branch by the [TestMu AI Documentation](https://testmu.ai/support/docs/) team, the content builds and deploys to a staging site. This allows you to review and test your content thoroughly on a server, rather than a local build, prior to merging your code to production. \ No newline at end of file +```bash +git clone https://github.com/LambdaTest/documentation && cd documentation +npm install --legacy-peer-deps +``` + +### Run locally + +Start the dev server with hot reload: + +```bash +npm start +``` + +The site runs at `http://localhost:3000`. Stop the server with `Ctrl + C`. + +### Build and verify links + +Before opening a PR, run a production build to catch broken links and missing images: + +```bash +npm run build +npm run serve +``` + +The build flags issues per file. Fix them, rebuild, and re-serve to verify. + +### Publishing workflow + +The repo uses two branches: + +- `stage`: staging environment, used for review before production +- `main`: production + +Workflow: + +1. Branch off `stage` and make your changes. +2. Open a PR against `stage` and tag the docs team for review. +3. Once merged, verify your changes on the staging site. +4. When the feature is ready for production, share the related PRs with the docs team. They will merge to `main`. + +Merges to `main` deploy to the live documentation site. + +## Contributions + +Contributions are welcome. Open an issue to discuss your idea before submitting a pull request. When reporting bugs, include your Node.js version, OS, and a link to the affected doc page. + +## TestMu AI (Formerly LambdaTest) Community + +Connect with testers and developers in the [TestMu AI Community](https://community.testmuai.com/). Ask questions, share what you are building, and discuss best practices in test automation and DevOps. + +## TestMu AI (Formerly LambdaTest) Certifications + +Earn free [TestMu AI Certifications](https://www.testmuai.com/certifications/) for testers, developers, and QA engineers. Validate your skills in Selenium, Cypress, Playwright, Appium, Espresso and more. Industry-recognized, shareable on LinkedIn, and built by practitioners, not marketers. + +## Learning Resources by TestMu AI (Formerly LambdaTest) + +Learn modern testing through tutorials, guides, videos, and weekly updates: + +* [TestMu AI Blog](https://www.testmuai.com/blog/) +* [TestMu AI Learning Hub](https://www.testmuai.com/learning-hub/) +* [TestMu AI on YouTube](https://www.youtube.com/@TestMuAI) +* [TestMu AI Newsletter](https://www.testmuai.com/newsletter/) + +## LambdaTest is Now TestMu AI + +On **January 12, 2026**, [LambdaTest evolved to TestMu AI](https://www.testmuai.com/lambdatest-is-now-testmuai/), the world's first fully autonomous **Agentic AI Quality Engineering Platform**. + +Same team. Same infrastructure. Same customer accounts. All existing LambdaTest logins, scripts, capabilities, and integrations continue to work without change. + +👉 Find the new home for [LambdaTest](https://www.testmuai.com). + +### How LambdaTest Evolved into TestMu AI + +In 2017, we launched LambdaTest with a simple mission: make testing fast, reliable, and accessible. As LambdaTest grew, we expanded into Test Intelligence, Visual Regression Testing, Accessibility Testing, API Testing, and Performance Testing, covering the full depth of the testing lifecycle. + +As software development entered the AI era, testing had to evolve, too. We rebuilt the architecture to be AI-native from the ground up, with autonomous agents that **plan, author, execute, analyze, and optimize tests** while keeping humans in the loop. The platform integrates with your repos, CI, IDEs, and terminals, continuously learning from every code change and development signal. + +That evolution earned a new name: **TestMu AI**, built for an AI-first future of quality engineering. TestMu is not a new name for us. It is the name of our annual community conference, which has brought together 100,000+ quality engineers to discuss how AI would reshape testing, long before that became an industry norm. + +What started as a high-performance cloud testing platform has transformed into an AI-native, multi-agent system powering a connected, end-to-end quality layer. That evolution defined a new identity: LambdaTest evolved into TestMu AI, built for an AI-first future of quality engineering. + +## Support + +Got a question? Email [support@testmuai.com](mailto:support@testmuai.com) or chat with us 24x7 from our chat portal. diff --git a/assets/images/mobile-app-testing/ai-test-case-generator-walkthrough.mp4 b/assets/images/mobile-app-testing/ai-test-case-generator-walkthrough.mp4 new file mode 100644 index 000000000..ab24e8dc8 Binary files /dev/null and b/assets/images/mobile-app-testing/ai-test-case-generator-walkthrough.mp4 differ diff --git a/custom.js b/custom.js index e5fd882e8..b70d34a79 100644 --- a/custom.js +++ b/custom.js @@ -150,16 +150,41 @@ } } window.sendAmplitudeEvents = sendAmplitudeEvents; + window.addEventListener('click', function (event) { - if (event.target.matches(".menu__link")) { - let params = window.location.href.split('/'); + // Sidebar navigation tracking + const menuLink = event.target.closest(".menu__link"); + // Search result click tracking + const searchHit = event.target.closest(".DocSearch-Hit a"); + + // Determine which link was actually clicked + const clickedLink = searchHit || menuLink; + if (clickedLink && clickedLink.href) { + const page_title = + clickedLink.getAttribute("title") || + clickedLink.textContent?.trim() || + ""; + const page_url = clickedLink.href || ""; + const urlObj = new URL(page_url, window.location.origin); + const page_path = + urlObj.pathname.split("/").filter(Boolean).pop() || ""; + + let params = window.location.href.split("/"); let pageName = params[params.length - 2]; - if (pageName.includes('hyperexecute')) { - sendAmplitudeEvents('HYP: page changed - docs', { + + if (pageName.includes("hyperexecute")) { + sendAmplitudeEvents("HYP: page changed - docs", { pageName, - }) + }); + } else { + sendAmplitudeEvents("Page Viewed", { + page_title, + page_url, + page_path, + }); } } + if (event.target.matches(".clean-btn")) { let target = event.target || event.srcElement; let codeblock = target.closest('.lambdatest__codeblock'); diff --git a/docs/generate-test-cases.md b/docs/generate-test-cases.md index c5d5f3eef..388896033 100644 --- a/docs/generate-test-cases.md +++ b/docs/generate-test-cases.md @@ -141,6 +141,7 @@ The Memory Layer operates automatically in the background, you can choose to ena ::: --- + ## Generate Test Cases: Step-by-Step ### Step 1: Open the AI Test Case Generator @@ -423,6 +424,16 @@ The **Create and Automate** option requires KaneAI access. If you do not have Ka --- +## Video Walkthrough + +Watch the video below for a quick walkthrough of the AI Test Case Generator in action. + + + +--- + ## Frequently Asked Questions **Can I undo a change made through the Conversation Layer?** diff --git a/docs/kaneai-gps-location.md b/docs/kaneai-gps-location.md index fdebfec44..d62e7d954 100644 --- a/docs/kaneai-gps-location.md +++ b/docs/kaneai-gps-location.md @@ -1,9 +1,9 @@ --- id: kaneai-gps-location -title: GPS location mocking for Mobile App Authoring +title: GPS Location Mocking for Mobile App and Mobile Browser Authoring hide_title: false sidebar_label: GPS Location -description: Learn how to use GPS Location Override feature in KaneAI for testing location-based mobile app functionalities +description: Learn how to use GPS Location Override feature in KaneAI for testing location-based functionalities in Mobile App and Mobile Browser sessions keywords: - testmu ai automation - testmu ai kaneai @@ -41,7 +41,7 @@ canonical: https://www.testmuai.com/support/docs/kaneai-gps-location// }} > -> This document provides detailed instructions for utilizing GPS Location Override feature in KaneAI's mobile app testing. It covers how to set GPS coordinates during session initialization to test location-based application behavior accurately. +> This document provides detailed instructions for utilizing the GPS Location Override feature in KaneAI for both Mobile App and Mobile Browser testing. It covers how to set GPS coordinates at the start of a session as well as within a running session to test location-based application behavior accurately. ## Overview @@ -49,6 +49,8 @@ Testing location-based application behavior (such as geo-restricted content, reg The GPS Location Override feature solves this problem by allowing users to explicitly define latitude and longitude values during session initialization. This ensures consistent, repeatable, and deterministic testing of location-dependent scenarios on supported mobile devices. +This feature is supported for both **Mobile App** and **Mobile Browser** sessions. For both sessions, GPS location can also be changed within a running session. + ## How To Use ### Select GPS location while Authoring App Test @@ -78,10 +80,8 @@ GPS coordinates can be verified ## Limitations -- GPS override is applied only during authoring session initialization -- GPS coordinates cannot be changed while the session is running -- Replay/Edit sessions reuse GPS values from the original session -- Currently not supported for Mobile Browser sessions +- GPS override is applied only during session initialization and can be changed mid-session. +- Replay/Edit sessions reuse GPS values from the original session. ## Troubleshooting @@ -98,16 +98,6 @@ GPS coordinates can be verified - Ensure values are passed as valid numbers or numeric strings -### Feature Not Working in Mobile Browser - -**Issue:** GPS override Currently not suported for mobile browser testing. - -**Reason:** -- GPS Location Override is not currently supported for Mobile Browser sessions - -**Workaround:** -- Use Mobile App testing for GPS-dependent scenarios - --- > Have any feedback or request? Reach out to us via [support@testmu.ai](mailto:support@testmu.ai) and we would be happy to hear from you. \ No newline at end of file diff --git a/docs/timeouts-issues-and-resolutions.md b/docs/timeouts-issues-and-resolutions.md index 9dc4605f0..5795c444e 100644 --- a/docs/timeouts-issues-and-resolutions.md +++ b/docs/timeouts-issues-and-resolutions.md @@ -30,6 +30,8 @@ There could be several reasons related to a timeouts. We are going to highlight If the Selenium grid detects inactivity for 120 seconds then you may encounter the below error: **Idle Timeout :** Test was terminated because grid hasn't received any requests for 120 second. To avoid this use idleTimeout using desired capabilities. e.g: set 'idleTimeout':'270′. +Once the default or user-defined idle timeout period is reached, our platform marks the test in the `idle_timeout` state. This will not necessarily happen exactly at the idle timeout duration. The system identifies and marks such tests on a best-effort basis, so it may take some additional time in certain cases. We recommend defining the `idleTimeout` capability according to your requirements. + The timeout could also occur due to network latency, or due to improper declaration of driver.quit(). **Resolution :** You can extend the 120 second idle timeout limit up to 1800 seconds by declaring the idleTimeout capability in your desired capabilities of a test suite. diff --git a/docs/tunel-release-notes.md b/docs/tunel-release-notes.md index e93fd0471..b81fc4dcb 100644 --- a/docs/tunel-release-notes.md +++ b/docs/tunel-release-notes.md @@ -41,6 +41,10 @@ import BrandName, { BRAND_URL } from '@site/src/component/BrandName'; }) }} > +## Version 3.2.28 (24th May 2026) +- **Security Updates and Stability Fixes** + - Security Fixes for CVE + - Fixed SOCKS5 proxy authentication when --proxy-user / --proxy-pass are supplied ## Version 3.2.25 (28th Dec 2025) - **Security Updates and Stability Fixes** - Security Fixes for CVE diff --git a/docusaurus.config.js b/docusaurus.config.js index ba94c5519..1de253ab9 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -3,7 +3,8 @@ import { themes as prismThemes } from 'prism-react-renderer'; module.exports = { title: 'TestMu AI (Formerly LambdaTest)', tagline: 'Ensure your web-apps work seamlessly on every desktop and mobile browsers.', - url: 'https://www.testmuai.com', + url: 'https://www.lambdatest.com', + noIndex: true, baseUrl: '/support/', onBrokenLinks: 'throw', favicon: 'img/favicon.ico',