<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Kishor Munot on Medium]]></title>
        <description><![CDATA[Stories by Kishor Munot on Medium]]></description>
        <link>https://medium.com/@kishor-munot?source=rss-40482fbdd50f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*6KDIy9z8CYoQne9v.jpg</url>
            <title>Stories by Kishor Munot on Medium</title>
            <link>https://medium.com/@kishor-munot?source=rss-40482fbdd50f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 07:48:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kishor-munot/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Nvidia — Is this change will create new chapter in Technolgy?]]></title>
            <link>https://kishor-munot.medium.com/nvidia-is-this-change-will-create-new-chapter-in-technolgy-83bd975baed3?source=rss-40482fbdd50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/83bd975baed3</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ai-bubble]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[nivida]]></category>
            <category><![CDATA[technology-news]]></category>
            <dc:creator><![CDATA[Kishor Munot]]></dc:creator>
            <pubDate>Sat, 14 Nov 2026 21:31:01 GMT</pubDate>
            <atom:updated>2026-11-14T21:31:01.462Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/738/0*SBPMs_n4GmJeyXmP" /></figure><p>Hello Everyone,</p><p>Today, I’m discussing a major development in the technology industry that took place last week. The news is related to <strong>NVIDIA</strong>, one of the world’s leading technology companies, which has played a significant role in advancing technology and transforming human lives.</p><p>According to the announcement made on Thursday, <strong>NVIDIA CEO Jensen Huang</strong> is stepping down from his position as head of the chipmaker he co-founded 33 years ago. Under his leadership, NVIDIA grew into a company valued at approximately $4 trillion and became one of the key drivers of the artificial intelligence boom.</p><p>The sudden resignation of the co-founder and CEO of NVIDIA — a company regarded as a primary architect of artificial intelligence (AI) technology — is not merely a leadership change within a single firm; it is a highly significant event with the potential for far-reaching consequences. These include impacts on the global tech economy, the technological rivalry between the <strong>United States and China</strong>, and the polarized debate surrounding the so-called ‘<strong>AI bubble</strong>’ — a phenomenon characterized by excessive investment and inflated expectations within the AI ​​sector.</p><blockquote>Discuss in detail</blockquote><p>We all know that there is intense technological competition between the United States and China, particularly in the semiconductor and artificial intelligence sectors.</p><p>Earlier this year, the United States imposed restrictions on the export of advanced AI chips to China, aiming to limit China’s access to critical technologies used in developing advanced AI systems and conducting research.</p><p>However, an interesting development has recently emerged in the industry. Reports suggest that a Singapore-based company called Megaspeed procured approximately 4.8 billion chips through a tender process. This has raised concerns and prompted an investigation into how these chips were supplied and whether any third country acted as an intermediary in the transaction.</p><p>This situation raises important questions about international trade regulations, semiconductor supply chains, export controls, and the ongoing technological rivalry between the United States and China.</p><p>The global technology and industrial world has witnessed an unexpected shock that nobody could have imagined.</p><p>The CEO of NVIDIA, a leading company in the field of Artificial Intelligence (AI), has reportedly been forced to step down following a major controversy. He had become a victim of a major <em>honey trap</em>. An investigation conducted by an independent board of directors reportedly brought several shocking details to light.</p><p>‘Honey trapping’ is not a new concept in international intelligence operations. It has been used for a long time to obtain sensitive information from influential individuals. However, in today’s world, corporate espionage has become increasingly sophisticated.</p><p>In the business world, companies do not compete only by collecting information about their competitors. They also try to understand their competitors’ strategies, future plans and technological developments. The primary objective is to gain a competitive advantage.</p><p>In the past, companies relied on publicly available information and traditional market research. Today, however, corporate espionage has become much more sophisticated, involving psychological manipulation, emotional exploitation and other techniques.</p><p>Modern corporate espionage is not limited to stealing confidential documents or business information. It can also involve obtaining information about a company’s future plans, strategic decisions, technological innovations and intellectual property.</p><p>In some cases, individuals may be manipulated into revealing confidential information, which can then be used to influence a company’s business operations and decision-making processes.</p><blockquote>Upcoming change in the tech industry</blockquote><p>The leadership change will change the face of AI or not will tell future but if NVIDIA changes its investment strategy, it could affect AI startups and infrastructure companies that depend on its financing and ecosystem support.</p><p>IDC’s assessment is that near-term AI infrastructure demand and supply are largely committed, so the bigger uncertainties concern longer-term technology roadmaps, financing and customer relationships.</p><p>Companies like AMD, Google, Amazon, and Broadcom stand to gain a significant boost from these developments, as they now have the opportunity to attract AI developers; their custom TPU chips could become increasingly important, and their custom AI chips and networking solutions may take on strategic significance.</p><p><strong>From washing dishes at a Denny’s to building a $4 trillion technology giant, </strong>Huang has led Nvidia for nearly 33 years — and made one of Silicon Valley’s defining entrepreneurial stories.</p><p>But the “cult-style” leaders at Silicon Valley — including Huang, Meta’s Mark Zuckerberg and Elon Musk — also reflect the concentration of market power that tech companies enjoy. Technology stocks now account for nearly 40 percent of the S&amp;P 500’s total market value.</p><p>That is likely to rise when AI companies Anthropic and OpenAI also go public.</p><p>And in the absence of a clear succession plan, things could go awry, sending jitters among investors — a concern which Nvidia highlighted itself in its annual review for this year.</p><p>Under the risk factors dealing with its dependence on key personnel, Nvidia’s report noted that the company is “highly dependent on the services of our longstanding executive team”.</p><p>The world’s technology industry is closely watching NVIDIA’s upcoming third-quarter earnings meeting on <strong>November 17, 2026</strong>.</p><p>With NVIDIA navigating a major leadership transition, the meeting could offer important signals about the company’s future direction, AI infrastructure investments, semiconductor demand and the competitive landscape.</p><p>The implications may extend well beyond NVIDIA, influencing AI companies, cloud providers, semiconductor manufacturers and technology investors worldwide.</p><h3>November–December 2026: Market Uncertainty</h3><ul><li>AI companies assess the impact of NVIDIA’s leadership transition.</li><li>Investors closely monitor quarterly earnings, management announcements and future business guidance.</li><li>Competitors communicate their AI chip strategies and seek opportunities in the evolving market.</li></ul><h3>January–February 2027: Strategic Adjustment</h3><ul><li>AI infrastructure customers reassess supplier diversification strategies.</li><li>Alternative AI chip platforms receive increased attention.</li><li>Technology companies focus on computing efficiency, infrastructure costs and reducing dependence on individual chip suppliers.</li></ul><h3>March–April 2027: Competition and Innovation</h3><ul><li>Alternative AI accelerators could gain wider adoption.</li><li>Cloud providers may expand their in-house AI chip development strategies.</li><li>Smaller, more efficient AI models could become increasingly important in reducing computing costs.</li></ul><h3>May 2027: Direction Becomes Clearer</h3><ul><li>NVIDIA’s permanent leadership arrangements may become clearer.</li><li>The industry can better assess continuity in NVIDIA’s technology roadmap and innovation strategy.</li><li>Global AI infrastructure investments and competitive positioning may be reassessed.</li></ul><blockquote>Final thoughts</blockquote><p>The next chapter of the AI revolution may be about more than leadership. It may be about who leads the next wave of innovation. The real story to watch is not simply what happens to NVIDIA, but how the entire global AI ecosystem evolves in response. How will the United States and China respond to these developments in next 6 months, strengthen their AI capabilities, and turn the evolving semiconductor landscape into new opportunities for technological growth and innovation these type question are present in the world of tech so answer is still in the pipeline and the picture will clear in upcoming days.</p><p>Thanks you</p><p>Share your thoughts and feedbacks in the comments below.</p><blockquote><strong>#Must Read</strong></blockquote><p><a href="https://kishor-munot.medium.com/software-testing-and-ai-ml-as-a-good-recipe-3d6be79afb98">Software Testing and AI/ML as a good recipe. | Medium</a></p><p><a href="https://kishor-munot.medium.com/cypress-ai-copilot-automation-with-a-grain-of-salt-story-ede683490a2b">Cypress -AI-Copilot- Automation -with a grain of salt story.</a></p><p><a href="https://kishor-munot.medium.com/playwright-in-simple-way-discuss-2117d3c8b563">Playwright — In Simple ways — Just Disucss</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83bd975baed3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cypress 16.2.0 arrived with playwrite features?]]></title>
            <link>https://kishor-munot.medium.com/cypress-16-2-0-arrived-with-playwrite-features-25a35c1e3294?source=rss-40482fbdd50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/25a35c1e3294</guid>
            <category><![CDATA[cypress]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[playwright-automation]]></category>
            <category><![CDATA[latest-updates]]></category>
            <category><![CDATA[automation-testing]]></category>
            <dc:creator><![CDATA[Kishor Munot]]></dc:creator>
            <pubDate>Sun, 25 Oct 2026 21:31:01 GMT</pubDate>
            <atom:updated>2026-10-25T21:31:01.657Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YQnMLIeDwuJN_UDr.png" /><figcaption>Cypress</figcaption></figure><p>Hello everyone,</p><p>The world of test automation is evolving faster than ever! And now AI is also changing the game, so everyone’s goal should be to keep challenging ourselves and stay updated with new fruitful ways..</p><p>Today, just diving into the latest Cypress updates and exploring its evolving features, because it looks like Cypress and Playwright are gradually shaping a better experience for the entire automation industry by learning from each other’s advancements and continuously enhancing their own capabilities.</p><p>Cypress has just arrived with version 16.2.0, and it looks like the Cypress team is keeping a close eye on Playwright, while the Playwright team has also introduced a feature in its last update that was previously associated with Cypress. So, let’s dive into the latest updates and find out whether Cypress is still in the game or if its era is coming to an end!</p><p>Writing reliable end-to-end tests is an essential part of delivering a high-quality web application. Cypress provides powerful querying capabilities, and with the introduction of cy.getByRole(), developers can select elements based on their ARIA roles and accessible names.</p><p>This approach encourages accessibility-focused testing while making test code easier to read, understand, and maintain.</p><pre>cy.getByRole(&#39;tab&#39;, { name: &#39;Billing&#39; });</pre><p>This query selects the element exposed with the tab role and the accessible name Billing.</p><p>Instead of relying on CSS selectors or implementation-specific attributes, you can write tests that describe the purpose of the element.</p><ul><li>Supports role and accessible-name queries.</li><li>Excludes hidden elements by default; use { hidden: true } to include them.</li><li>Supports { native: false } to include elements with explicit role attributes.</li><li>Automatically retries until assertions pass.</li><li>Provides helpful errors listing available roles and accessible names.</li></ul><blockquote>Latest Updates</blockquote><ul><li>Chrome, Chromium, and Edge now intercept test traffic through the browser’s native network instead of routing it through Cypress. Some cy.intercept() behaviors differ, including the availability of req.httpVersion and compression headers. Use forceHttp1 temporarily if you need the legacy network path during migration.</li><li>Cypress no longer supports Node.js 20 and Node.js 25. It now requires Node.js 22.x, 24.x, or 26 and above. Update your local development environment and CI pipelines to a supported version.</li><li>Cypress.env() has been removed. Use Cypress.expose() for non-sensitive values that need browser access and cy.env() for sensitive values that should remain in the Node.js process.</li><li>The cy.exec() command and execTimeout configuration option have been removed. Use cy.task() with taskTimeout for supported Node.js operations, avoiding dependencies on the operating system&#39;s shell or terminal.</li><li>The cy.end() command has been removed because Cypress automatically starts a new command chain when another cy command begins. Existing .end() calls can generally be deleted.</li><li>The default keystrokeDelay has changed from 10 milliseconds to 0, improving the performance of typing-heavy test suites. If your tests rely on the previous delay, set keystrokeDelay: 10 in your Cypress configuration or through Cypress.Keyboard.defaults().</li><li>The cypress info command no longer prints proxy environment variables such as HTTP_PROXY, HTTPS_PROXY, and NO_PROXY, or variables prefixed with CYPRESS_. This makes its output safer to share when reporting bugs.</li><li>The cypress tap run command now reports that the spec is running and directs users to cypress tap status to check progress.</li><li>The TypeScript documentation for the multiple option in .dblclick() now correctly shows its default value as true, matching the command&#39;s actual behavior. This update improves documentation accuracy and helps developers understand how double-click actions behave when multiple elements match.</li><li>When cy.contains() starts a new command chain, it now appears as a parent command in the Cypress Command Log. Previously, it was always displayed as a child command, even when used independently.</li><li>TypeScript now supports options objects for six Cypress commands that already accepted them at runtime. This fixes type errors when using .nextUntil(), .parentsUntil(), .prevUntil(), .each(), .spread(), and .scrollIntoView().</li></ul><pre>cy.get(&#39;.item&#39;).each({ log: false }, ($el) =&gt; {<br>  // Process each element<br>});<br><br>cy.get(&#39;.target&#39;).scrollIntoView({<br>  offset: { top: 100 }</pre><p>Cypress has improved the performance of the .closest() command when working with subjects containing many elements inside the Shadow DOM. This optimization helps tests run more efficiently when traversing complex component structures, improving performance and responsiveness in applications that use web components.</p><blockquote>Is Cypress Dead?</blockquote><p>Cypress is dead!!! or is it gearing up for its next big comeback? I think Cypress and Playwright are keeping a very close eye on each other’s moves, and soon, the competition could get even more intense, pushing the test automation game faster and further than ever before!</p><p>Cypress 16 was showcased at the Cypress conference, hinting that they might be gearing up to change the game soon! 🚀 Hopefully, they’ll come back stronger than ever. Let’s wait and watch for the announcement of Cypress 17.0!</p><p>Thank you,</p><p>Share your thoughts on the same.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25a35c1e3294" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Load It. Stress It. Break It. Fix It. Make It Shine — Performance Testing]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://kishor-munot.medium.com/load-it-stress-it-break-it-fix-it-make-it-shine-performance-testing-59d9d02042d8?source=rss-40482fbdd50f------2"><img src="https://cdn-images-1.medium.com/max/1200/1*1vUUwmDZi8Fx95alcdpXcQ.png" width="1200"></a></p><p class="medium-feed-snippet">Hello Everyone,</p><p class="medium-feed-link"><a href="https://kishor-munot.medium.com/load-it-stress-it-break-it-fix-it-make-it-shine-performance-testing-59d9d02042d8?source=rss-40482fbdd50f------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://kishor-munot.medium.com/load-it-stress-it-break-it-fix-it-make-it-shine-performance-testing-59d9d02042d8?source=rss-40482fbdd50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/59d9d02042d8</guid>
            <category><![CDATA[performance-testing]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[load-testing]]></category>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[k6]]></category>
            <dc:creator><![CDATA[Kishor Munot]]></dc:creator>
            <pubDate>Mon, 31 Aug 2026 21:31:01 GMT</pubDate>
            <atom:updated>2026-08-31T21:31:01.302Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[JustDiscuss : Playwright with Agentic AI]]></title>
            <link>https://kishor-munot.medium.com/justdiscuss-playwright-with-agentic-ai-418dbf39befa?source=rss-40482fbdd50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/418dbf39befa</guid>
            <category><![CDATA[playwright-automation]]></category>
            <category><![CDATA[playwrights]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Kishor Munot]]></dc:creator>
            <pubDate>Tue, 21 Jul 2026 21:31:01 GMT</pubDate>
            <atom:updated>2026-07-21T21:31:01.546Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*FsT5taFo3BheJ6iOe9wyhw.png" /><figcaption>Playwright</figcaption></figure><p>Hello Everyone,</p><p>Today, we’re going to discuss Playwright and how it integrates with different AI agents, exploring how this combination is transforming browser automation and reshaping the future of software testing and web automation.</p><p>Playwright with agentic AI generally refers to combining Playwright with an AI agent that can understand goals, plan actions, interact with web pages, and adapt when things change.</p><p>For decades, the internet has been a human-first environment. Every button, form, login page, and checkout flow was designed for a pair of human eyes and a pair of human hands. APIs were the machine’s doorway into digital systems — but APIs don’t exist for everything. Millions of web applications have no API. They only speak HTML, JavaScript, and clicks.</p><p>This is where playwright enters the picture for Agentic AI .</p><p>Agentic AI Systems — AI that takes action , makes decisions , and completes multi step tasks autonomously need to interact with the real digital world .They need to browse , search , fill forms , extract data , navigate applications and respond to what they see on a page.Playwright gives them exactly that : a programmatic ,reliable , production ready way to control a real web browser and interact with any website.</p><p>Instead of scripting every click manually, you give the agent a task such as:</p><blockquote><em>“Log into the CRM, find all customers whose subscription expires this month, and download the report.”</em></blockquote><p>The AI decides which buttons to click, which forms to fill, and how to recover if the page layout changes.</p><h3>How it works</h3><p>A typical architecture looks like this:</p><pre>User Goal<br>      │<br>      ▼<br>+------------------+<br>| LLM / AI Agent   |<br>| - Plans actions  |<br>| - Understands UI |<br>| - Decides next step<br>+------------------+<br>      │<br>      ▼<br>+------------------+<br>| Playwright       |<br>| Browser Control  |<br>| - Click          |<br>| - Type           |<br>| - Navigate       |<br>| - Screenshot     |<br>| - Extract text   |<br>+------------------+<br>      │<br>      ▼<br>Website</pre><p>The agent follows a loop:</p><ol><li>Observe the current page.</li><li>Decide the next action.</li><li>Execute it using Playwright.</li><li>Check the result.</li><li>Repeat until the goal is complete.</li></ol><h3>Example</h3><p>Traditional Playwright:</p><pre>await page.goto(&quot;https://example.com/login&quot;);<br>await page.fill(&quot;#email&quot;, &quot;user@example.com&quot;);<br>await page.fill(&quot;#password&quot;, &quot;password&quot;);<br>await page.click(&quot;button[type=submit]&quot;);</pre><p>Agentic approach:</p><pre>Goal:<br>&quot;Login and download the latest invoice.&quot;<br><br>Agent:<br>1. Open website<br>2. Find login form<br>3. Enter credentials<br>4. Navigate to Billing<br>5. Find newest invoice<br>6. Download PDF</pre><p>The code mainly provides browser capabilities, while the AI determines the sequence of actions.</p><p>Software testing is evolving. Traditional automation frameworks help speed up repetitive tasks, but they often break with small changes, require constant maintenance, and struggle to keep up with complex systems.</p><p><strong>Agentic AI</strong> offers a new paradigm: intelligent, autonomous agents that can perceive, reason, act, and learn, making test automation more resilient, adaptive, and scalable. For QA engineers, this isn’t just a buzzword, it’s a practical shift in how we approach testing.</p><blockquote>Playwright: The Game Changer or Critical or Risk Buster for Agentic AI?</blockquote><p>Agentic AI is redefining how software interacts with digital systems. Unlike traditional automation, which follows predefined scripts, AI agents can understand objectives, reason through complex scenarios, make decisions, and adapt their actions based on changing conditions. However, intelligence alone is not enough — AI agents also need a reliable way to interact with applications. This is where Playwright plays a pivotal role.</p><p>Playwright acts as the execution engine for AI agents, enabling them to interact with web applications just as a human user would. It allows agents to navigate websites, click buttons, fill out forms, upload and download files, extract information, and validate outcomes across modern web applications.</p><p>Modern websites are dynamic and continuously evolving. Elements load asynchronously, user interfaces change frequently, and workflows often span multiple pages, tabs, and authentication steps. Playwright is designed to handle these complexities with features such as auto-waiting, resilient locators, cross-browser compatibility, and comprehensive debugging capabilities. These features make it an ideal foundation for AI-driven browser automation.</p><p>When integrated with Agentic AI, Playwright enables a new generation of intelligent automation. Instead of relying solely on rigid, predefined scripts, AI agents can interpret a high-level objective, determine the sequence of actions required to accomplish it, execute those actions through Playwright, observe the results, and adapt if something unexpected occurs.</p><p>For example, rather than writing hundreds of lines of automation code to retrieve a monthly sales report, an AI agent can receive a simple instruction such as, <em>“Log in to the CRM, generate the sales report for the previous month, and download it.”</em> The agent plans the workflow, while Playwright performs the browser interactions needed to complete the task.</p><p>This combination extends beyond software testing. Organizations are increasingly using Agentic AI and Playwright for business process automation, customer support workflows, data extraction, compliance checks, quality assurance, and intelligent web assistants. Together, they bridge the gap between AI reasoning and real-world execution.</p><p>In essence, Agentic AI provides the intelligence to understand and plan tasks, while Playwright provides the reliable browser automation capabilities to execute them. Together, they are enabling a new era of autonomous, intelligent web automation.</p><blockquote>The Architecture of a Playwright-Powered AI Agent</blockquote><p>A typical agentic AI system built with Playwright follows a loop:</p><pre>Observe → Think → Act → Observe → Think → Act → ...</pre><p>Playwright handles the <strong>Observe</strong> and <strong>Act</strong> steps. The AI model (GPT-4, Claude, Gemini, or any LLM) handles the <strong>Think</strong> step.</p><pre>┌──────────────────────────────────────────────┐<br>│              AI Agent Loop                   │<br>│                                              │<br>│  ┌──────────┐   ┌──────────┐   ┌─────────┐ │<br>│  │ Observe  │─▶ │  Think  │──▶│   Act   │ │<br>│  │(Playwright│  │  (LLM)   │   │Playwright│ │<br>│  │screenshot│   │          │   │click/fill│ │<br>│  │+ DOM)    │   │ &quot;What    │   │/navigate │ │<br>│  │          │   │ should I │   │          │ │<br>│  └──────────┘   │ do next?&quot;│   └──────────┘ │<br>│       ▲         └──────────┘        │       │<br>│       └────────────────────────────┘        │<br>└──────────────────────────────────────────────┘</pre><pre>import asyncio<br>import base64<br>import anthropic<br>from playwright.async_api import async_playwright</pre><pre>client = anthropic.Anthropic()</pre><pre>async def observe(page) -&gt; dict:<br>    &quot;&quot;&quot;Capture the current state of the browser page.&quot;&quot;&quot;<br>    # Take a screenshot for visual understanding<br>    screenshot_bytes = await page.screenshot(full_page=False)<br>    screenshot_b64 = base64.b64encode(screenshot_bytes).decode()</pre><pre>    # Also extract the page structure as text<br>    title = await page.title()<br>    url = page.url</pre><pre>    # Extract all interactive elements<br>    interactive = await page.evaluate(&quot;&quot;&quot;() =&gt; {<br>        const elements = [];<br>        document.querySelectorAll(&#39;button, a, input, select, textarea&#39;).forEach((el, i) =&gt; {<br>            const rect = el.getBoundingClientRect();<br>            if (rect.width &gt; 0 &amp;&amp; rect.height &gt; 0) {<br>                elements.push({<br>                    index: i,<br>                    tag: el.tagName.toLowerCase(),<br>                    text: el.innerText?.slice(0, 80) || &#39;&#39;,<br>                    type: el.type || &#39;&#39;,<br>                    placeholder: el.placeholder || &#39;&#39;,<br>                    href: el.href || &#39;&#39;,<br>                    id: el.id || &#39;&#39;,<br>                    name: el.name || &#39;&#39;<br>                });<br>            }<br>        });<br>        return elements;<br>    }&quot;&quot;&quot;)</pre><pre>    return {<br>        &quot;screenshot_b64&quot;: screenshot_b64,<br>        &quot;title&quot;: title,<br>        &quot;url&quot;: url,<br>        &quot;interactive_elements&quot;: interactive<br>    }<br></pre><pre>async def think(observation: dict, goal: str, history: list) -&gt; dict:<br>    &quot;&quot;&quot;Ask the LLM what action to take given the current observation.&quot;&quot;&quot;<br>    messages = history + [{<br>        &quot;role&quot;: &quot;user&quot;,<br>        &quot;content&quot;: [<br>            {<br>                &quot;type&quot;: &quot;image&quot;,<br>                &quot;source&quot;: {<br>                    &quot;type&quot;: &quot;base64&quot;,<br>                    &quot;media_type&quot;: &quot;image/png&quot;,<br>                    &quot;data&quot;: observation[&quot;screenshot_b64&quot;]<br>                }<br>            },<br>            {<br>                &quot;type&quot;: &quot;text&quot;,<br>                &quot;text&quot;: f&quot;&quot;&quot;<br>Current page: {observation[&#39;title&#39;]} — {observation[&#39;url&#39;]}</pre><pre>Goal: {goal}</pre><pre>Interactive elements on page:<br>{observation[&#39;interactive_elements&#39;]}</pre><pre>Decide the next action. Respond with JSON:<br>{{<br>  &quot;action&quot;: &quot;click&quot; | &quot;fill&quot; | &quot;goto&quot; | &quot;done&quot; | &quot;extract&quot;,<br>  &quot;target&quot;: &quot;description of element to interact with&quot;,<br>  &quot;value&quot;: &quot;text to type (for fill action) or URL (for goto)&quot;,<br>  &quot;reasoning&quot;: &quot;why this action moves toward the goal&quot;,<br>  &quot;done&quot;: false<br>}}<br>&quot;&quot;&quot;<br>            }<br>        ]<br>    }]</pre><pre>    response = client.messages.create(<br>        model=&quot;claude-opus-4-5&quot;,<br>        max_tokens=1024,<br>        system=&quot;You are a web navigation agent. Analyze the page and decide the next action to achieve the goal. Always respond with valid JSON.&quot;,<br>        messages=messages<br>    )</pre><pre>    import json<br>    return json.loads(response.content[0].text)<br></pre><pre>async def act(page, action: dict) -&gt; str:<br>    &quot;&quot;&quot;Execute the action decided by the LLM.&quot;&quot;&quot;<br>    action_type = action.get(&quot;action&quot;)<br>    target = action.get(&quot;target&quot;, &quot;&quot;)<br>    value = action.get(&quot;value&quot;, &quot;&quot;)</pre><pre>    if action_type == &quot;goto&quot;:<br>        await page.goto(value)<br>        await page.wait_for_load_state(&quot;networkidle&quot;)<br>        return f&quot;Navigated to {value}&quot;</pre><pre>    elif action_type == &quot;click&quot;:<br>        # Try multiple locator strategies<br>        try:<br>            locator = page.get_by_role(&quot;button&quot;, name=target)<br>            if await locator.count() &gt; 0:<br>                await locator.first().click()<br>            else:<br>                locator = page.get_by_text(target)<br>                await locator.first().click()<br>        except Exception:<br>            await page.locator(f&quot;text={target}&quot;).first().click()<br>        await page.wait_for_load_state(&quot;domcontentloaded&quot;)<br>        return f&quot;Clicked: {target}&quot;</pre><pre>    elif action_type == &quot;fill&quot;:<br>        locator = page.get_by_placeholder(target)<br>        if await locator.count() == 0:<br>            locator = page.get_by_label(target)<br>        await locator.first().fill(value)<br>        return f&quot;Filled &#39;{target}&#39; with &#39;{value}&#39;&quot;</pre><pre>    elif action_type == &quot;extract&quot;:<br>        text = await page.evaluate(&quot;document.body.innerText&quot;)<br>        return text[:5000]  # Return first 5000 chars</pre><pre>    return &quot;No action taken&quot;<br></pre><pre>async def run_agent(goal: str, start_url: str, max_steps: int = 15):<br>    &quot;&quot;&quot;Main agentic loop.&quot;&quot;&quot;<br>    async with async_playwright() as pw:<br>        browser = await pw.chromium.launch(headless=True)<br>        ctx = await browser.new_context(<br>            viewport={&quot;width&quot;: 1280, &quot;height&quot;: 800}<br>        )<br>        page = await ctx.new_page()<br>        await page.goto(start_url)</pre><pre>        history = []<br>        results = []</pre><pre>        for step in range(max_steps):<br>            print(f&quot;\n--- Step {step + 1} ---&quot;)</pre><pre>            # Observe<br>            observation = await observe(page)</pre><pre>            # Think<br>            action = await think(observation, goal, history)<br>            print(f&quot;Action: {action[&#39;action&#39;]} | Reasoning: {action[&#39;reasoning&#39;]}&quot;)</pre><pre>            # Check if done<br>            if action.get(&quot;done&quot;) or action.get(&quot;action&quot;) == &quot;done&quot;:<br>                print(&quot;Agent completed the goal!&quot;)<br>                break</pre><pre>            # Act<br>            result = await act(page, action)<br>            results.append(result)<br>            print(f&quot;Result: {result}&quot;)</pre><pre>            # Update history<br>            history.append({<br>                &quot;role&quot;: &quot;assistant&quot;,<br>                &quot;content&quot;: str(action)<br>            })</pre><pre>        await browser.close()<br>        return results<br></pre><pre># Run the agent<br>asyncio.run(run_agent(<br>    goal=&quot;Find the price of the MacBook Pro 14-inch on Apple&#39;s website&quot;,<br>    start_url=&quot;https://www.apple.com&quot;<br>))</pre><blockquote>Future Enhancements</blockquote><ul><li>Switch from free-form prompt to YAML or JSON plan schema</li><li>Build Lang Graph-based branching flows (if-else, retries, confirmations)</li><li>Add screenshot validation after each step</li><li>Integrate with CI/CD to validate staging and prod automatically.</li></ul><blockquote>The cost of intelligence</blockquote><p>Running an agent loop on every PR isn’t free. Each healing cycle, each planning step, each code generation pass burns tokens. For a team running 200 PRs a week, that adds up.</p><p>The smart play: don’t make everything agentic. Keep your stable, high-confidence tests as static Playwright specs. Reserve the agent loop for flaky tests, new features, and areas with frequent UI churn. Some teams we’ve talked to run agents only on failed tests during a second pass, cutting token spend by 70% while keeping coverage intact.</p><p>Watch your CI/CD bill. The agents are capable, but “run agents on everything” is a 2025 mistake you’ll regret in 2026.</p><p>Here’s a 2026 pro-tip most teams learn the hard way: MCP tools have a context tax. Connecting to 5–10 MCP servers can eat 15–20% of your LLM’s context window before you send a single command. Tool descriptions, schemas, and capabilities all count against your tokens.</p><p>The workaround is “Code Mode.” Instead of the agent calling tools directly, it writes code that calls the tools. One code block replaces dozens of tool invocations, and the context overhead drops dramatically. It’s less elegant, but it’s how teams run complex agent workflows without hitting token limits.</p><blockquote>Final Thoughts</blockquote><p>Agentic AI is more than a testing tool — it’s a bridge between intent and execution. It empowers non-technical users to validate mission-critical workflows using natural language, backed by real browser automation.</p><p>Playwright Test Agents mark the beginning of AI-assisted testing. They automate the repetitive parts of QA and show what’s possible with structured AI orchestration.</p><p>But the future goes further. Real-time, natural language testing will adapt and learn with every product change.</p><p>As this space continues to evolve, we’re likely to see more teams building their own MCPs, fine-tuning agents for their environments, and rethinking what “automation” truly means. This isn’t just about adopting new tools — it’s about reimagining how we deliver quality in a world where software is constantly changing.</p><p>That said, it’s also important to think of what could go wrong. Agentic systems are still maturing, and there are real risks such as misinterpretation of prompts or test intents, inconsistent behaviours across environments, without proper validation could lead to missed defects or false confidence.</p><p>To mitigate these risks, we need robust validation layers, fallback mechanisms, and clear boundaries for autonomous execution.</p><p>This shift also has implications for test engineers. Rather than replacing them, it can elevate their roles such as designing intelligent workflows, focussing more on prompt engineering, scenario design, and validating agent behavior and shaping how these systems learn, adapt, and scale.</p><p>In short, Agentic AI and MCP have the potential to transform test automation from a task-driven activity into a context based intelligent process that aligns more closely with the modern software development.</p><p>Thank you,</p><p>Feel free to share your feedback and thoughts regarding this article in the comments section below.</p><blockquote><strong>#MustRead</strong></blockquote><p><a href="https://kishor-munot.medium.com/playwright-in-simple-way-discuss-2117d3c8b563">Playwright — In simple way — Discuss | Medium</a></p><p><a href="https://kishor-munot.medium.com/software-testing-and-ai-ml-as-a-good-recipe-3d6be79afb98">Software Testing and AI/ML as a good recipe. | Medium</a></p><p><a href="https://kishor-munot.medium.com/chatgpt-developers-qa-4fa72b55d51f">ChatGPT — Cypress — QA- Developers. | Medium</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=418dbf39befa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MobileWright (Playwright for Mobile)]]></title>
            <link>https://kishor-munot.medium.com/mobilewright-playwright-for-mobile-cd63dd1cc1a7?source=rss-40482fbdd50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd63dd1cc1a7</guid>
            <category><![CDATA[playwright-automation]]></category>
            <category><![CDATA[appium]]></category>
            <category><![CDATA[mobilewright]]></category>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[mobile-testing]]></category>
            <dc:creator><![CDATA[Kishor Munot]]></dc:creator>
            <pubDate>Sun, 31 May 2026 21:31:00 GMT</pubDate>
            <atom:updated>2026-05-31T21:31:00.855Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/910/1*hgtzhTNOlD0Vq_pENB9dBg.png" /><figcaption>Playwright for mobile</figcaption></figure><p>Hello Readers,</p><p>We are currently making a significant contribution to our product development by effectively utilizing ‘Playwright’ within our framework to automate the ‘manual use cases’ in our project. Simultaneously, I am endeavoring to share my experiences and insights with you by publishing a some articles; furthermore, with the aim of expanding my own knowledge, I regularly read a wide range of articles on the subject of ‘automation.’ The purpose of writing this article is to share a piece of news I read last week — something I felt compelled to pass on to you. While many of you may already be aware of it, let us use this article as a platform to delve deeper into the details and engage in a discussion regarding the subject. My attention was suddenly captured by the term <strong>‘MobileWright’</strong> while I was reading various articles on diverse topics last week. I had a vague idea about this, as Playwright had hinted at it a few years earlier. However, when I came across it again after a long time, it had become major news that caught everyone’s attention. After reviewing some of the facts surrounding it, it appears highly probable that this development will bring about a significant transformation in the field of ‘Mobile Automation’ in the near future.</p><blockquote>Mobile Automation</blockquote><p>Mobile Application Testing is one of the most important aspects of modern software testing. It enables testers to automate repetitive tasks, ensuring that mobile apps function as expected across multiple devices, platforms, and user scenarios. Testing apps manually across different environments can be time consuming and prone to human error, so automation helps save time and increases efficiency.</p><p>In the world of 2026, a mobile app is often the primary or only interface between a brand and its customer. As an expert who has watched this landscape evolve, I can tell you that the cost of a single crash is no longer just a bug report; it is a permanent loss of user trust. This post will delve into the essentials of mobile app test automation, why it is crucial for successful app development, and how it can streamline the testing process. Whether you are building an Android or iOS app, knowing the best practices and tools for <a href="https://www.testriq.com/automation-testing-services">A</a>utomation Testing can help you create robust and high quality apps.</p><blockquote>Why mobile Automation is Important</blockquote><p>The digital market is crowded, and users have zero patience for failure. Here are the primary reasons why automation has become a non negotiable standard in 2026.</p><h3>1. Efficiency and Speed</h3><p>Automated tests can run 24/7, helping you speed up the testing process significantly. Mobile app automation allows you to test your app continuously as new code is developed, ensuring that bugs are detected quickly and resolved early. This is a core component of the modern DevOps pipeline where code is released multiple times a day.</p><h3>2. Accuracy and Consistency</h3><p>With mobile app test automation, your testing is more precise, and it becomes easier to detect bugs and <a href="https://www.testriq.com/security-testing">Security Testing</a> issues consistently across various devices and operating systems. Human testers, as brilliant as they are, can get tired. A script never gets bored of checking a login field for the thousandth time.</p><h3>3. Increased Coverage</h3><p>Automation allows you to simulate multiple users and test different configurations, ensuring compatibility across devices, browsers, and OS versions. In 2026, we are dealing with folding screens, wearable integrations, and varied network speeds. Manual testing simply cannot cover this spectrum efficiently.</p><h3>4. Cost-Effective in the Long Run</h3><p>Once the automation framework is set up, you can run tests repeatedly without additional costs, which reduces the need for manual testing and minimizes the chances of expensive post release bugs. Investing in managed testing services ensures that this framework is built correctly from day one.</p><blockquote>Back To MobileWright</blockquote><p>Today, Appium stands as a strong and powerful automation tool. However, with the launch of MobileWright by Playwright, a new era has begun in the world of mobile testing. If you’ve ever automated a web app with Playwright, you know what a breath of fresh air it was — no flaky sleeps, clean APIs, deterministic execution. The gap between automation tools and mobile testing is likely to be bridged by MobileWright soon.</p><p>In today’s era of automation, Appium stands as an extremely powerful tool; nevertheless, we often encounter certain challenges while automating Android and iOS applications using it. Nowadays, mobile applications are being developed using cutting-edge technologies; consequently, <strong>MobileWright </strong>will facilitate the automation process by providing support for such applications.</p><blockquote>Set up for Playwright with example</blockquote><pre>npm install mobilewright @mobilewright/test<br>npm init mobilewright@latest</pre><p>After installing Node.js and installing the above ‘dependencies’ via the terminal, you will receive a basic framework structure from ‘Mobile Weight’.</p><pre>Sample-project/<br>├── mobilewright.config.ts<br>├── package.json<br>└── tests/<br>    └── example.test.ts</pre><p>Then, according to your requirments you need to set your config and then start for the automation.</p><blockquote>Example</blockquote><pre>import {test,expect} from &#39;@mobilewright/test&#39;;<br><br>test(&#39;login&#39;,async ({screen}) ={<br>await screen.getByLabel(&#39;Email&#39;).fill(&#39;example@gmail.com&#39;);<br>await screen.getByLabel(&#39;Password&#39;).fill(&#39;Abcdef&#39;);<br>await screen.getByRole(&#39;button&#39;{name:&#39;Sign In&#39;}).tap();<br>await screen.getByText(&#39;Welcome to Mobile Testing&#39;).toBeVisible();<br><br>})</pre><p>In the below example test, I have shared the ‘Login Test’ used in mobile automation with MobileWright. The interesting aspect here is that we can use the Playwright API within MobileWrite; therefore, for those who have experience with Playwright, MobileWrite can offer an excellent experience.</p><blockquote>Appium vs MobileWright</blockquote><p>It would be incorrect to claim that MobileWright is superior to Appium; however, Appium certainly has certain pain points — particularly the constant API changes introduced in every new version, which have led to instability and confusion over time. MobileWright addressed some of these issues or pain points in mobile automation, in the near future, with the aid of its AI agents, it is set to resolve some of the most critical challenges within the field of mobile automation. Mobile Weight is still in the ‘beta’ stage and is available to beta testers. Many Beta testers are sharing valueable feedbacks and soon we will see MobileWright upgraded and stable version for automation testers.</p><p>Feel free to share your feedback and thoughts regarding this blog in the comments section below. Also, be sure to share your thoughts on ‘MobileWright’; and if I have missed any points, please let me know here — so that we can all learn together.</p><p>Thank you.</p><blockquote>#MustRead</blockquote><p><a href="https://kishor-munot.medium.com/playwright-in-simple-way-discuss-2117d3c8b563">Playwright — In simple way — Discuss | Medium</a></p><p><a href="https://kishor-munot.medium.com/user-authentication-in-automation-with-cypress-and-playwright-c87bc75c136e">User Authentication in automation with Cypress and Playwright | Medium</a></p><p><a href="https://kishor-munot.medium.com/2026-docker-with-cypress-15-and-playwright-1-58-99794028afe6">2026 : Docker with Cypress 15 and Playwright 1.58 | Medium</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd63dd1cc1a7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[API Testing — Playwright]]></title>
            <link>https://kishor-munot.medium.com/api-testing-playwright-8a619c53a5e4?source=rss-40482fbdd50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a619c53a5e4</guid>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[api-testing]]></category>
            <category><![CDATA[cypress]]></category>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[playwrights]]></category>
            <dc:creator><![CDATA[Kishor Munot]]></dc:creator>
            <pubDate>Sun, 03 May 2026 21:31:01 GMT</pubDate>
            <atom:updated>2026-05-03T21:31:01.279Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SXJ_4icqGm36XqoCX_QQfA.jpeg" /></figure><p>Hello Everyone,</p><p>Today, We’re going to explore API testing using Playwright, diving deeper into the topic to build a stronger understanding of how it works. We’ve already discussed API testing with Selenium and Cypress in earlier blogs, and I will also include links to those at the end of this article so you can check them out.</p><blockquote>Playwright — API testing</blockquote><p>Playwright is widely known for browser automation, it also offers powerful features for API testing, making it a versatile tool for end-to-end testing. By using <a href="https://playwright.dev/">Playwright</a>, testers can efficiently validate API endpoints, perform authentication checks, and seamlessly integrate API tests with UI tests to ensure consistent functionality across the entire application. API testing with Playwright allows for the testing of various HTTP methods, including GET, POST, PUT, and DELETE requests, enabling comprehensive validation of data flow and business logic. Additionally, Playwright supports handling complex authentication scenarios, such as token-based and OAuth authentication. This guide will explain why Playwright is an excellent choice for API testing, how to set it up and provide detailed examples of requests, authentication handling, and best practices for effective and efficient API testing.</p><blockquote>API in simple words</blockquote><p>Imagine you’re using a food delivery service.</p><ul><li>You place an order in the app</li><li>The app sends your request to the restaurant</li><li>The restaurant prepares the food</li><li>The delivery arrives at your home</li></ul><p>Now, forget the app screen. Focus only on the <strong>communication happening in the background</strong>.</p><p>That communication is like an API.</p><h3>Correct Order</h3><p>You order: “1 Pizza”</p><h3>✔️ You receive: “1 Pizza”<br> 👉 Test passes (everything works)</h3><h3>❌ 2. Wrong Order</h3><p>You order: “1 Pizza”</p><p>❌ You receive: “1 Burger”<br> 👉 Test fails (wrong response)</p><h3>⚠️ 3. Missing Information</h3><p>You just say: “Send food”</p><p>❌ Restaurant asks: “What food?”<br> 👉 System should handle missing details properly</p><h3>🔐 4. Unauthorized Request</h3><p>Someone else tries to pick up your order</p><p>❌ Delivery is denied<br> 👉 System should ensure security</p><h3>⏱️ 5. Delay</h3><p>You order food</p><p>❌ It arrives after 3 hours<br> 👉 System should respond in a reasonable time</p><blockquote>API Testing using playwright</blockquote><p>In API testing, different HTTP methods are used for different operations. <strong>GET</strong> is used to retrieve data, while <strong>POST</strong> is used to create new data. <strong>PUT</strong> is used to completely replace existing data, whereas <strong>PATCH</strong> is used to update only specific parts of the data. <strong>DELETE</strong> is used to remove data from the database. Please checkout below examples used in Playwright while doing API testing.</p><pre>import { test, expect, request } from &#39;@playwright/test&#39;;<br>import { test, expect } from &#39;@playwright/test&#39;;<br><br>test(&#39;GET users&#39;, async ({ request }) =&gt; {<br>  const response = await request.get(&#39;/api/users/1&#39;);<br><br>  expect(response.status()).toBe(200);<br><br>  const body = await response.json();<br>  expect(body.id).toBe(1);<br>});</pre><pre>test(&#39;POST create user&#39;, async ({ request }) =&gt; {<br>  const response = await request.post(&#39;/api/users&#39;, {<br>    data: {<br>      name: &#39;John&#39;,<br>      email: &#39;john@test.com&#39;<br>    }<br>  });<br><br>  expect(response.status()).toBe(201);<br><br>  const body = await response.json();<br>  expect(body.name).toBe(&#39;John&#39;);<br>});</pre><pre>test(&#39;PUT update user&#39;, async ({ request }) =&gt; {<br>  const response = await request.put(&#39;/api/users/1&#39;, {<br>    data: {<br>      name: &#39;John Updated&#39;,<br>      email: &#39;john_updated@test.com&#39;<br>    }<br>  });<br><br>  expect(response.status()).toBe(200);<br><br>  const body = await response.json();<br>  expect(body.name).toBe(&#39;John Updated&#39;);<br>});</pre><pre>test(&#39;PATCH update user email&#39;, async ({ request }) =&gt; {<br>  const response = await request.patch(&#39;/api/users/1&#39;, {<br>    data: {<br>      email: &#39;newemail@test.com&#39;<br>    }<br>  });<br><br>  expect(response.status()).toBe(200);<br><br>  const body = await response.json();<br>  expect(body.email).toBe(&#39;newemail@test.com&#39;);<br>});</pre><p>Many QA engineers use Playwright for API testing because it is comfortable to use and offers powerful features.</p><p><strong>Features and capabilities to address Selenium’s limitations and challenges.</strong> Playwright provides them plenty for AQA teams.</p><ol><li><strong>QA teams can test developed software in different browser versions, and operating systems, as well as emulate a real device</strong> such as a mobile phone or tablet to make sure it provides consistent behavior across diverse user test environments and works as expected.</li><li><strong>Playwright is really fast and flexible</strong> and might be tailored to specific requirements of many testing projects.</li><li><strong>The learning curve of Playwright is fast.</strong> QA teams can start write tests in JavaScript with ease reducing the time required for <a href="https://testomat.io/blog/test-automation-with-playwright-definition-and-benefits-of-this-testing-framework/">test automation</a> coverage.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*bz4e2qRV08bCexm0.png" /></figure><p>A <strong>status code</strong> is a number returned by a server to tell you what happened to your request — whether it worked, failed, or needs further action.</p><p><strong>Common Status Codes</strong></p><p><strong>✅ Success (2xx)</strong><br>200 OK → Request successful<br>201 Created → New data created<br>204 No Content → Success, but no data returned<br><strong>⚠️ Client Errors (4xx)<br></strong>400 Bad Request → Invalid input<br>401 Unauthorized → Authentication required<br>403 Forbidden → Access denied<br>404 Not Found → Resource doesn’t exist<br><strong>❌ Server Errors (5xx)<br></strong>500 Internal Server Error → Something broke on server<br>502 Bad Gateway → Invalid response from another server<br>503 Service Unavailable → Server is down or busy</p><p>Please share your valuable feedback about API testing, Playwright and Automation Testing. The best way to grow is to read, write, implement, and share.</p><blockquote><em>Here to make the community stronger by sharing our knowledge. Let me know your feedback into the comments so we can learn together.</em></blockquote><blockquote><strong>#MustRead</strong></blockquote><p><a href="https://blog.nonstopio.com/api-testing-mocking-api-response-request-6ea08aa1a4dc">API Testing — Mocking API Response &amp; Request |</a> Medium</p><p><a href="https://kishor-munot.medium.com/playwright-in-simple-way-discuss-2117d3c8b563">Playwright — In simple way — Discuss | Medium</a></p><p><a href="https://blog.nonstopio.com/api-testing-discuss-in-detail-with-rest-assured-1d7c14b5e40e">API Testing with REST-assured. | </a>Medium</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a619c53a5e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Playwright — In simple way — Discuss]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://kishor-munot.medium.com/playwright-in-simple-way-discuss-2117d3c8b563?source=rss-40482fbdd50f------2"><img src="https://cdn-images-1.medium.com/max/646/1*92iTr102toytVNCYbF2oGA.png" width="646"></a></p><p class="medium-feed-snippet">Hello Readers,</p><p class="medium-feed-link"><a href="https://kishor-munot.medium.com/playwright-in-simple-way-discuss-2117d3c8b563?source=rss-40482fbdd50f------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://kishor-munot.medium.com/playwright-in-simple-way-discuss-2117d3c8b563?source=rss-40482fbdd50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2117d3c8b563</guid>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[selenium]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[playwrights]]></category>
            <dc:creator><![CDATA[Kishor Munot]]></dc:creator>
            <pubDate>Tue, 31 Mar 2026 21:31:01 GMT</pubDate>
            <atom:updated>2026-03-31T21:31:01.271Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[2026 : India AI Impact Summit : Opportunities, Challenges and Learnings]]></title>
            <link>https://kishor-munot.medium.com/2026-india-ai-impact-summit-opportunities-challenges-and-learnings-f02d056330a2?source=rss-40482fbdd50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f02d056330a2</guid>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[ai-impact-summit-2026]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[artficial-intelligence]]></category>
            <dc:creator><![CDATA[Kishor Munot]]></dc:creator>
            <pubDate>Sun, 01 Mar 2026 21:31:00 GMT</pubDate>
            <atom:updated>2026-03-01T21:31:00.599Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*eRg_i2WgLEQ96PJx5lhSKw.jpeg" /><figcaption>India AI Impact Summit 2026</figcaption></figure><p>Hello Readers,</p><p>In a nation where the Cricket World Cup is celebrated like a grand festival and conversations usually revolve around cricket and sports, something remarkable happened. In February 2026, the India AI Impact Summit was organized at Bharat Mandapam in New Delhi.</p><p>At a time when cricket fever traditionally dominates discussions, people across the country — on college campuses, in corporate offices, on public transport, and over morning and evening tea — were talking more about the AI Summit than the game itself.</p><p>This shift reflects the spirit of a new India — a nation ready to make its mark in artificial intelligence alongside leading countries of the world, and committed to building a future that is innovative, secure, and transformative.</p><blockquote>Introduction — AI Summit</blockquote><p>Dozens of countries have participated in these annual gatherings to discuss AI. At the first event, held at Bletchley Park in the U.K., an AI safety-focused dialogue took place, with India represented by then <strong>Minister of State for Electronics and Information Technology Rajeev Chandrasekhar.</strong> Currently, no international organisation oversees these gatherings; participating countries typically pass the baton to next year’s summit. The 2024 event was held in Seoul, and the most recent AI Action Summit took place in Paris in February 2025, with Prime Minister Narendra Modi co-chairing alongside President Emmanuel Macron. At the Paris summit, the multilateral AI dialogue underwent a notable shift when U.S. Vice President J.D. Vance vocally rejected a safety-first approach, arguing instead for an emphasis on innovation and unrestricted investment in frontier research and technology commercialisation. The next event is to be hosted by Geneva, Switzerland, in 2027.</p><p>While previous leaders mostly talked about safety risks and regulatory concerns in the developed world, New Delhi wanted to change the global AI agenda by focusing on three main areas: <strong>Deployment</strong>, <strong>Democratization</strong>, and <strong>Sovereignty</strong>.</p><p>The summit, which was based on the themes of <strong>People</strong>, <strong>Planet</strong>, and <strong>Progress</strong>, was the start of India’s ambitious “Sovereign AI” doctrine. The goal of this state-led industrial policy is to make India less reliant on American and Chinese foundational models by building up its own “Bharat” Large Multimodal Models (LMMs) and computational infrastructure.</p><blockquote>Dawn of Artificial Intelligence</blockquote><p>At <strong>Bharat Mandapam in New Delhi</strong>, from <strong>February 16 to 18</strong>, the <strong>India AI Impact Summit 2026</strong> was held. The event attracted global attention, with hundreds of discussions, exhibitions, and participation from representatives of more than a hundred countries, along with several heads of state.</p><p>The summit showcased the extraordinary capabilities of <strong>Artificial Intelligence (AI)</strong>. At the same time, it also raised subtle concerns about the future of humanity due to the growing power of AI.</p><p>Many people saw many leaders from the world such as <strong>Prime Minister Narendra Modi</strong>, <strong>French President Emmanuel Macron</strong>, and <strong>Brazilian President Luiz Inácio Lula da Silva</strong> were present. Major technology leaders also attended, including <strong>Sam Altman (OpenAI)</strong>, <strong>Sundar Pichai (Google)</strong>, <strong>Dario Amodei (Anthropic)</strong>, and <strong>Demis Hassabis (Google DeepMind)</strong>.</p><p>Globally, both China and the United States are developing major AI technologies. Although China did not participate in the India AI Summit 2026 for certain reasons, it is undoubtedly paying close attention to the key issues discussed at the summit. The USA America has made its position clear and, in line with its position, the world should use its stack for research and other purposes.Stack means data. After World War II, America increased its influence through military equipment, and its symbolic form began to appear in the modern era.</p><h3>Democratization of AI Development”</h3><p>India’s position is unique. Data, computing resources, and technological tools are not equally accessible to all countries — and India acknowledges this reality. The declaration adopted at the end of the summit 2026 held in new delhi india clearly mentions the concept of democratization.</p><p>Countries like India face major challenges such as employment generation and achieving self-reliance in technology. Pakistan, Bangladesh, Indonesia, and several African nations are lagging behind. In such a situation, if these countries are not included in the mainstream of AI-driven progress, their development prospects in the future could weaken further.</p><blockquote>Three Sovereign AI Models Unveiled in Summit 2026</blockquote><p>One of the defining moments of the <strong>India AI Impact Summit 2026</strong> was the unveiling of three major indigenous AI models under the broader vision of Sovereign AI development.</p><ul><li><strong>Sarvam AI</strong> introduced two large language models trained entirely in India, demonstrating advanced reasoning and programming capabilities.</li><li><strong>Gnani.ai</strong> launched a multilingual voice model capable of functioning across 12 Indian languages, even under low-bandwidth conditions.</li><li><strong>BharatGen</strong> unveiled a 17-billion-parameter multilingual foundational model optimized for Indic languages and open-source collaboration.</li></ul><p>These launches mark India’s transition from being a technology consumer to becoming a technology creator. By strengthening local innovation ecosystems, the IndiaAI Mission aims to ensure that India contributes meaningfully to global AI research while maintaining strategic autonomy. The success of these models reinforces India’s ambition to lead the Global South in the AI movement.</p><blockquote>Some News from Summit 2026</blockquote><ul><li>India earmarked <a href="https://techcrunch.com/2026/02/14/india-doubles-down-on-state-backed-venture-capital-approving-1-1b-fund/">$1.1 billion for its state-backed venture capital fund</a>. The fund will invest in artificial intelligence and advanced manufacturing startups across the country.</li><li>OpenAI CEO Sam Altman said India accounts for more than <a href="https://techcrunch.com/2026/02/15/india-has-100m-weekly-active-chatgpt-users-sam-altman-says/">100 million weekly active ChatGPT users</a>, second only to the U.S. He also said Indians account for the most students using ChatGPT.</li><li>OpenAI said it will open two new offices in India in Bengaluru and Mumbai.</li><li>Blackstone has picked up a majority stake in Indian AI startup Neysa as part of a <a href="https://techcrunch.com/2026/02/15/blackstone-backs-neysa-in-up-to-1-2b-financing-as-india-pushes-to-build-domestic-ai-compute/">$600 million equity fundraise</a>. Teachers’ Venture Growth, TVS Capital, 360 ONE Asset, and Nexus Venture Partners also invested. The company now plans to raise another $600 million in debt, and deploy more than 20,000 GPUs.</li><li>Bengaluru-based C2i, which is building a power solution for data centers, raised <a href="https://techcrunch.com/2026/02/15/as-ai-data-centers-hit-power-limits-peak-xv-backs-indian-startup-c2i-to-fix-the-bottleneck/">$15 million in a Series A round from Peak XV</a>, with participation from Yali Deeptech and TDK Ventures.</li><li>HCL CEO Vineet Nayyar said Indian IT companies <a href="https://economictimes.indiatimes.com/ai/ai-insights/ai-impact-summit-profit-comes-first-not-jobs-for-it-companies-warns-vineet-nayyar-as-ai-boom-could-worsen-job-crisis/articleshow/128405154.cms">will focus on turning profits and not being job creators</a>. These comments come as <a href="https://www.reuters.com/world/india/indian-shares-seen-lower-amid-global-it-selloff-ahead-us-inflation-2026-02-13/">Indian IT stocks dip</a> as fears of AI disrupting the IT services sector burgeon.</li><li>Vinod Khosla, founder of Khosla Ventures, said that industries like IT services and BPOs (Business Process Outsourcing) can “almost completely disappear” within five years because of AI. He told <a href="https://www.hindustantimes.com/india-news/aisummit-2026-it-bpo-services-will-disappear-in-five-years-says-venture-capitalist-khosla-101771182147907.html">Hindustan Times</a> that 250 million young people in India should be selling AI-based products and services to the rest of the world.</li><li>AMD is teaming up with Tata Consultancy Services (TCS) to <a href="https://www.amd.com/en/newsroom/press-releases/2026-2-15-amd-and-tcs-to-bring-state-of-the-art-helios-rac.html">develop</a> rack-scale AI infrastructure based on AMD’s “Helios” platform.</li><li>Anthropic said that it is opening its first office in India in the city of Bengaluru. The company said that the country is the second biggest user of Claude after the U.S.</li><li>Anthropic is <a href="https://techcrunch.com/2026/02/17/as-ai-jitters-rattle-it-stocks-infosys-partners-with-anthropic-to-build-enterprise-grade-ai-agents/">partnering with IT giant Infosys to deploy Claude models</a> and tools like Claude code to Indian enterprises. To begin, both will deploy AI tools in the telecommunications sector with a dedicated Anthropic Center of Excellence.</li><li>Indian AI company Sarvam teased its upcoming smart glasses under the name Sarvam Kaze. The company has released several models in the past few weeks, including a dubbing model, a speech-to-text model, a text-to-speech model, and a vision model for Optical Character Recognition (OCR).</li></ul><blockquote>Challenges in the path of India’s future</blockquote><p>India’s goals for this conference were clear. To showcase India’s AI capabilities to the world, to highlight the potential of the Indian market, and to provide an alternative vision to the world at a time when the US and China are at the forefront. An indirect attempt to dispel the perception that only the US and China can dominate artificial intelligence and that the world has to rely on its research.</p><p>India has increasingly seen the opportunities and risks presented by AI. At the same time, India’s path over the next 5 to 10 years, along with some of its current limitations, has also become clear. If India wants to progress rapidly, it should learn from examples such as the Chinese-made robot showcased by Galangoti University, the long queues to enter the Bharat Mandapam, and the uneasy barriers created by VIP culture among invited tourists from around the world. Infrastructure expansion must be matched by regulatory clarity. Skill development initiatives must reach beyond metropolitan centres. Ethical guidelines must be translated into enforceable standards. Furthermore, ensuring equitable access to AI benefits requires sustained public investment.</p><p>There were also practical lessons from the summit’s scale, managing large crowds, coordinating multiple sessions and balancing high-level diplomacy with grassroots engagement. These are growing pains of a country stepping into a leadership role.</p><blockquote>Final Conclusion : Secure,Safe and Advance truth</blockquote><p>The summit may well be remembered as a strategic inflection point in India’s technological journey. It consolidated India’s aspiration to be not just a participant but a shaper of the global AI order. By foregrounding inclusivity, responsibility and sovereignty, the summit articulated a model of AI development aligned with India’s democratic and developmental ethos.</p><p>The achievements, ranging from international endorsements and investment commitments to indigenous model launches and sectoral partnerships, provide tangible momentum. More importantly, the summit reframed the global conversation to include the priorities of emerging economies.</p><p>If sustained through policy continuity, infrastructure investment, skill development and ethical oversight, the outcomes of the summit could catalyse a new phase of economic and social transformation. In that sense, the summit was not merely an event; it was a declaration of intent, an assertion that India intends to help shape the future of AI in a manner that is inclusive, secure and development-oriented.</p><blockquote>Please share your feedback in the comments. I would like to hear your thoughts on Summit 2026 held in India, as well as your expectations for the next summit, which will be held in Geneva, Switzerland, in 2027.</blockquote><p>Thank you.</p><blockquote><strong><em>#MustRead</em></strong></blockquote><p><a href="https://kishor-munot.medium.com/software-testing-and-ai-ml-as-a-good-recipe-3d6be79afb98">Software Testing and AI/ML as a good recipe. | Medium</a></p><p><a href="https://kishor-munot.medium.com/latest-prompt-engineering-and-automation-testing-dd33df85b070">Latest : Prompt Engineering and Automation Testing | Medium</a></p><p><a href="https://kishor-munot.medium.com/cypress-15-0-artificial-intelligence-3760d4fba440">Cypress 15.0 — Artificial Intelligence | Medium</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f02d056330a2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2026 : Docker with Cypress 15 and Playwright 1.58]]></title>
            <link>https://kishor-munot.medium.com/2026-docker-with-cypress-15-and-playwright-1-58-99794028afe6?source=rss-40482fbdd50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/99794028afe6</guid>
            <category><![CDATA[playwrights]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[cypress]]></category>
            <dc:creator><![CDATA[Kishor Munot]]></dc:creator>
            <pubDate>Tue, 03 Feb 2026 22:01:01 GMT</pubDate>
            <atom:updated>2026-02-04T06:00:33.399Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XKEiq501okYifAYXYrnuQA.png" /></figure><p>Hello everyone,</p><p>We are currently working alongside AI and experiencing both its advantages and limitations. This process is helping us identify areas where greater effort is needed. Today’s discussion focuses on how we can minimize the challenges posed by rapidly evolving technology and effectively address them.</p><p>This article describes the benefits of using Docker in Cypress or Playwright, discusses in detail the current official images, and outlines the mechanism for building custom Docker images to run Cypress tests or Playwright tests in Docker containers deployed based on these images.</p><p>A question that often comes to mind is whether we really need Docker in the QA workflow. QA professionals are usually busy juggling multiple responsibilities and are often the final checkpoint in every deployment. So, the real question is: can Docker actually help reduce the effort required from QA?</p><blockquote>Docker</blockquote><p><strong>Docker is a platform that lets you package an application together with everything it needs to run</strong> — code, runtime, libraries, system tools, and settings — into a single unit called a <strong>container</strong>.</p><p>Think of a container as a <strong>lightweight, portable box</strong> that holds your app and its environment.</p><p>Docker is an open-source service for packaging, deploying, and running applications in an isolated containerized environment.</p><p>Docker is used in test automation to provide <strong>consistent, isolated, and scalable test environments</strong>, which helps eliminate the “it works on my machine” problem and streamlines the testing process, especially in CI/CD</p><h3>What problem does Docker solve?</h3><p>Without Docker:</p><ul><li>App works on developer’s laptop ❌</li><li>Breaks on server ❌</li><li>Different OS versions, libraries, configs cause issues ❌</li></ul><p>With Docker:</p><ul><li>Same container runs on <strong>laptop, server, cloud, CI/CD</strong> ✅</li><li>No “dependency hell” ✅</li><li>Easy setup and teardown ✅</li></ul><blockquote>Do we need Docker in our life?</blockquote><p>Let’s dive into a real-life example to understand how Docker can make a meaningful difference in everyone’s work</p><p>Imagine you’re cooking a meal and need to deliver it to different people, much like the famous dabbawalas in Mumbai, India.</p><p>Without Docker, you might simply send the recipe and instructions: “Use this stove, these spices, this pan, and make sure the temperature is right.” The problem is that every kitchen is different, so the meal might turn out differently — or not cook properly at all — depending on the equipment and ingredients available. With Docker, however, these issues are minimized, ensuring a consistent and high-quality outcome every time.</p><p>❌ Without Docker</p><p>You send <strong>just the recipe</strong>:</p><ul><li>“Use this stove”</li><li>“Use this pan”</li><li>“Make sure the gas pressure is right”</li><li>“Oh, and the spices must be <em>these exact brands</em>”</li></ul><p>Result:</p><ul><li>Tastes different in every kitchen</li><li>Sometimes doesn’t cook at all</li><li>Everyone blames the recipe 😅</li></ul><p>This is like sending <strong>only your app’s code</strong> and hoping it runs everywhere.</p><h3><strong>✅With Docker</strong></h3><p>You send a <strong>lunchbox</strong> 🍱 that already contains:</p><ul><li>The cooked food (your app)</li><li>The right spices (libraries)</li><li>The correct container (runtime)</li><li>Instructions already followed</li></ul><p>No matter whose kitchen it goes to:</p><ul><li>Home</li><li>Office</li><li>Restaurant</li><li>Another country</li></ul><p>The food tastes <strong>exactly the same</strong>.</p><p>That lunchbox = <strong>Docker container</strong></p><blockquote>Cypress and Playwright</blockquote><p>We all know the role of Cypress and Playwright in a QA professional’s workflow. If you want to explore them in more detail, check out the article below.</p><p><a href="https://kishor-munot.medium.com/selenium-cypress-and-playwrite-6e470938be4a">Cypress and Playwright | Medium</a></p><blockquote>Why Docker Matters: Benefits for Cypress and Playwright</blockquote><p>In modern automated testing, setting up and maintaining a test environment can often become a tedious task, especially when dealing with multiple dependencies and their configurations, different operating systems, libraries, tools, and their versions. Often in practice, we can encounter dependency conflicts, inconsistencies in environments, limitations in scalability and reproduction of errors that occur, etc., which ultimately leads to unpredictable and unreliable test results. Using Docker goes a long way in preventing most of these problems.</p><p>Today it is difficult to imagine the development of any web application without the participation of Docker. The usage of Docker containerization technologies brings a bunch of serious advantages for testing web applications, such as ensuring a consistent and isolated environment for running tests in each new run; independence from the parameters and settings of the system on which the tests are run; reliability, reproducibility, and predictability of test results when they are run in different environments, etc.</p><p>In particular, using Docker in Cypress or playwright testing can be very useful for several reasons:</p><ol><li>It ensures that tests run in an isolated test environment because the container in which the tests are run is self-contained from other containers and from the external environment. In this case, the tests are essentially independent of what is outside the container, which ensures the reliability and continuity of the tests in each new run. For example, in the case of deploying containers with tests locally, this means that the absence of Node.js, Cypress, any browser, or certain versions of them on the host computer will not become an obstacle to running Cypress tests.</li><li>Allows applications and Cypress or Playwright tests to be run locally on different host machines, as well as deployed to CI/CD pipelines and cloud infrastructure by providing a stable and consistent test environment. When moving a Docker image from one server to another, containers with the application itself and tests will work the same regardless of the operating system used, the presence of Node.js, Cypress, browsers, etc. This ensures reproducibility and predictability when running Cypress tests across different systems.</li><li>Frees us from having to install any dependencies outside of containers — on the servers that run the containers. Docker allows us to quickly deploy the containerized environment to run tests, so we do not need to install operating system dependencies, necessary browsers, and test frameworks every time.</li><li>Significantly simplifies the integration of Cypress or Playwright tests into the web application development process, embedding and deploying tests in various CI/CD pipelines, cloud services, etc., eliminating the need to troubleshoot compatibility issues during installation, reconfiguration, etc. In addition, Docker allows us to safely move tests between software deployment environments, for example, from a tester’s laptop to a stage or production environment.</li><li>Speeds up the testing process by reducing the total time for test runs. This is achieved through scaling, i.e., increasing the number of containers, running Cypress tests in different containers in parallel, parallel cross-browser testing capabilities using Docker Compose, etc.</li></ol><h3>A short dive into a cypress test project</h3><p>To demonstrate running tests in Docker containers, I’ll use “Cypress-Docker” — the simplest project with Cypress tests.</p><p>The project already has some dependencies installed — <em>Cypress 15.1.0</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*O_hcr0QXHXT3XR2p.png" /></figure><p>and there is also one <em>spec.cy.ts</em> file with a test suite of three trivial tests for the blog’s homepage:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*1eEI8BCZEzx9dq8U.png" /></figure><p>By running these tests in headless mode, we are convinced of the successful execution of the tests:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*p1bI4EUzbfFnDCYt.png" /></figure><p>Here we should pay attention to the environment settings when running tests locally on the computer — <em>Node.js 19.8.1</em>, <em>Cypress 12.12.0,</em> and browser Electron 106. Next, we will make sure that when running tests inside Docker containers, these settings will change depending on the content of the Docker images used. I also note that <a href="https://www.docker.com/products/docker-desktop/">Docker Desktop</a> is already installed locally.</p><h3>Running tests in Docker containers</h3><p>Now let’s look at how we can run our Cypress tests inside Docker containers using each of the official Cypress Docker images.</p><h3><a href="https://hub.docker.com/r/cypress/included/">CYPRESS/INCLUDED</a></h3><p>I would like to start with this image because, unlike the others, it includes all the dependencies of the operating system, pre-installed Cypress, and some browsers. This makes <em>cypress/included</em> available to use out of the box without the need to add additional layers. The image allows us to create containers and run Cypress tests in them using just single command.</p><p>To download an image from the Docker Hub, just run the following command in the terminal:</p><pre>&gt; docker pull cypress/included:12.12.0</pre><p>It’s important to note here that it’s a good idea to always add a specific image <em>tag</em> rather than relying on the default <em>(latest)</em> tag name because the latest version changes as new versions of the image are released. In the case of <em>cypress/included</em>, the tag name corresponds to the version of Cypress preinstalled inside it, for example, in my case, it is <em>12.12.0 (stable)</em>. Thus, if we do not specify the image version, then there is a chance that the tests will be run in different versions of Cypress since the containers for running the tests will be generated from images with different tags.</p><p>The presence of the specified image after it has finished downloading can be checked with a simple command:</p><pre>&gt; docker images</pre><p>The downloaded <em>cypress/included</em> image is shown first in the list of downloaded images:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/853/0*-Sqp664P72Kznac8.png" /></figure><p>To find out what this image contains, just execute the following command:</p><pre>&gt; docker run -it --entrypoint=cypress cypress/included:12.12.0 info</pre><p>As a result, we get information about the version of Node.js preinstalled in the image, Cypress, three browsers, as well as other characteristics:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*Zyth31Wlv_wx-DCi.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*i8Gamnei8EQgQf_f.png" /></figure><p>Next, to run our Cypress tests in a container, we need to initiate the creation of a new container from the downloaded image with the command below:</p><pre>&gt; docker run -it -v $PWD:/e2e -w /e2e cypress/included:12.12.0</pre><p>With this command, we have created a Docker container, which essentially means a writable layer on top of existing image layers. Let’s take a look at the structure of used command:</p><p>docker run means to create and run a container based on the specified image</p><p>-it — interactive terminal</p><p>-v $PWD:/e2e — map the contents of the directory inside the container to the contents of the current project directory, where $PWD is the absolute path to the current directory (root of the project), /e2e is the path to the directory inside the container</p><p>-w /e2e — set the working directory inside the container, where /e2e is the path to the specified directory</p><p>cypress/included:12.12.0 — an indication of the image on the basis of which the container will be created.</p><p>This command will create a Docker container in which Cypress will run tests on the built-in Electron browser. It is important to note that the <em>cypress/included</em> image includes ENTRYPOINT [&quot;cypress&quot; &quot;run&quot;] instruction, which automatically starts Cypress inside the container created from this image.</p><p>If desired, it is possible to supplement the command with --name flag to specify a specific name for the created container, as well as --rm flag to automatically delete the container after it is stopped:</p><pre>&gt; docker run -it -v $PWD:/e2e -w /e2e  --name cypress-tests --rm cypress/included:12.12.0</pre><p>At the same time, any additional arguments can be passed after the image name to control the behavior of Cypress, similar to how we run Cypress in headless mode without using Docker. So, we can specify a specific browser or spec file to run, configure recording parameters, run tests in parallel, etc. For example, to run tests in any of the browsers preinstalled in the image (Chrome, Edge, Firefox), it is enough to add to the command -b flag specifying the name of the browser:</p><pre>&gt; docker run -it -v $PWD:/e2e -w /e2e cypress/included:12.12.0 -b chrome</pre><p>Or if we assume that initially, the project has several spec files, then to run a specific file/files, we should pass to the command -s flag specifying the absolute path to the required file/files:</p><pre>&gt; docker run -it -v $PWD:/e2e -w /e2e cypress/included:12.12.0 -s cypress/e2e/spec.cy.ts</pre><p>Now that we know all those commands, let’s create a container and run our tests inside it using Chrome browser:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*6Dgf0yICvVh-9SXT.png" /></figure><p>And voila — we can now see that the specified test environment settings (Node.js 18.16.0, Cypress 12.12.0, Chrome 113) match the characteristics of the <em>cypress/included</em> image content while being different from the settings when we initially ran the tests locally. Thus, it took only single command to run the tests inside created Docker container.</p><p>I just ran my command, mounting my local Cypress project into the container:</p><pre># This command:<br># 1. Runs the cypress/included container.<br># 2. Mounts the local project into the container<br># 3. Executes the default &#39;cypress run&#39; command.</pre><pre>docker run -it \<br>-v $PWD:/e2e \<br>-w /e2e \<br>cypress/included:15.5.0 \<br>-s cypress/e2e/UI/*.js</pre><p>Container pulled the image, isolated the environment, ran the tests against my application, printed results to the console and then was immediately destroyed. This setup highlighted the benefits of Docker for test automation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*q-TcHAe3FQhtpwKu.png" /><figcaption>Quick comparison with Docker and Jenkins</figcaption></figure><blockquote>Final Thoughts</blockquote><h3>Final thoughts</h3><p>The official Cypress Docker images discussed in this article, as well as custom images created on their basis, greatly simplify the integration of Cypress tests into the development of modern web applications and increase the reliability and efficiency of the testing process in general. Providing a stable and consistent test environment and reproducibility across different software deployment environments greatly simplifies the setup and maintenance of automated tests, and makes it easier to detect and troubleshoot issues that arise.</p><p><strong>Docker</strong> wins easily for <strong>speed and simplicity</strong>. And if you’re building a <strong>long-term automation setup</strong> with versioned reports, plugins and deployment steps, <strong>Jenkins</strong> is the one.</p><p>That’s all for now. If you found this article helpful, share it with a friend or your community — someone else might benefit from it too. Feel free to share your thoughts as well; your feedback helps me grow and expand my knowledge.</p><p>Share your feedback and don’t forget to give a clap to the blog — after all, the journey is just as important as reaching the goal.</p><blockquote><strong>#MustRead</strong></blockquote><p><a href="https://kishor-munot.medium.com/latest-prompt-engineering-and-automation-testing-dd33df85b070">Latest : Prompt Engineering and Automation Testing</a></p><p><a href="https://kishor-munot.medium.com/cypress-ai-copilot-automation-with-a-grain-of-salt-story-ede683490a2b">Cypress -AI-Copilot- Automation -with a grain of salt story.</a></p><p><a href="https://kishor-munot.medium.com/speed-and-performance-lighthouse-with-cypress-part-1-2243405980ed">LightHouse With Cypress — Interesting Article</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99794028afe6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Windows App Automation | WinAppDriver | Experience]]></title>
            <link>https://kishor-munot.medium.com/windows-app-automation-winappdriver-experience-8391f1273c7a?source=rss-40482fbdd50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8391f1273c7a</guid>
            <category><![CDATA[winappdriver]]></category>
            <category><![CDATA[selenium]]></category>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[appium]]></category>
            <category><![CDATA[qa]]></category>
            <dc:creator><![CDATA[Kishor Munot]]></dc:creator>
            <pubDate>Tue, 13 Jan 2026 22:32:52 GMT</pubDate>
            <atom:updated>2026-01-13T22:32:52.132Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6u-30AUnEtLcPKkruO-Neg.jpeg" /><figcaption>Windows App Automation</figcaption></figure><p>Hello Readers,</p><p>This blog is a continuation (Part 2) of Windows application automation. In the previous article, I introduced Windows app automation and explained how to get started, including how to select the appropriate tool for a given automation requirement. I also discussed the advantages of Windows automation and provided an overview of <strong>WinAppDriver</strong>, which is used to automate Windows-based applications. You can check the article <a href="https://kishor-munot.medium.com/latest-1-windowsdesktop-app-automation-afac0b52980b">here..</a></p><blockquote><a href="https://kishor-munot.medium.com/latest-1-windowsdesktop-app-automation-afac0b52980b">#Latest #1 : WindowsDesktop App Automation</a></blockquote><p>In this article, we will cover all the important aspects, including my POC experience and a step-by-step guide on how to implement the framework from scratch for a windows based applications.</p><p>First, create a simple Maven project and add the required dependencies listed below.</p><pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot;<br> xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;<br> xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;<br> &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;<br><br> &lt;groupId&gt;eCube&lt;/groupId&gt;<br> &lt;artifactId&gt;eCubeWindowsApplicationTests&lt;/artifactId&gt;<br> &lt;version&gt;0.0.1-SNAPSHOT&lt;/version&gt;<br> &lt;packaging&gt;jar&lt;/packaging&gt;<br><br> &lt;name&gt;eCubeWindowsApplicationTests&lt;/name&gt;<br> &lt;url&gt;http://maven.apache.org&lt;/url&gt;<br><br> &lt;properties&gt;<br>  &lt;project.build.sourceEncoding&gt;UTF-8&lt;/project.build.sourceEncoding&gt;<br> &lt;/properties&gt;<br><br> &lt;dependencies&gt;<br>  &lt;!-- Selenium compatible with Appium 9.x --&gt;<br>  &lt;dependency&gt;<br>   &lt;groupId&gt;org.seleniumhq.selenium&lt;/groupId&gt;<br>   &lt;artifactId&gt;selenium-java&lt;/artifactId&gt;<br>   &lt;version&gt;3.141.59&lt;/version&gt;<br>  &lt;/dependency&gt;<br><br>  &lt;!-- Appium Java Client --&gt;<br>  &lt;!-- https://mvnrepository.com/artifact/io.appium/java-client --&gt;<br>  &lt;dependency&gt;<br>   &lt;groupId&gt;io.appium&lt;/groupId&gt;<br>   &lt;artifactId&gt;java-client&lt;/artifactId&gt;<br>   &lt;version&gt;7.3.0&lt;/version&gt;<br>  &lt;/dependency&gt;<br>  &lt;!-- TestNG --&gt;<br>  &lt;dependency&gt;<br>   &lt;groupId&gt;org.testng&lt;/groupId&gt;<br>   &lt;artifactId&gt;testng&lt;/artifactId&gt;<br>   &lt;version&gt;7.1.0&lt;/version&gt;<br>   &lt;scope&gt;test&lt;/scope&gt;<br>  &lt;/dependency&gt;<br>  &lt;!-- https://mvnrepository.com/artifact/mysql/mysql-connector-java --&gt;<br>  &lt;dependency&gt;<br>   &lt;groupId&gt;com.microsoft.sqlserver&lt;/groupId&gt;<br>   &lt;artifactId&gt;mssql-jdbc&lt;/artifactId&gt;<br>   &lt;version&gt;12.4.2.jre11&lt;/version&gt; &lt;!-- version may vary --&gt;<br>  &lt;/dependency&gt;<br>  &lt;dependency&gt;<br>   &lt;groupId&gt;io.github.bonigarcia&lt;/groupId&gt;<br>   &lt;artifactId&gt;webdrivermanager&lt;/artifactId&gt;<br>   &lt;version&gt;5.8.0&lt;/version&gt;<br>  &lt;/dependency&gt;<br>  &lt;dependency&gt;<br>   &lt;groupId&gt;com.googlecode.json-simple&lt;/groupId&gt;<br>   &lt;artifactId&gt;json-simple&lt;/artifactId&gt;<br>   &lt;version&gt;1.1.1&lt;/version&gt;<br>  &lt;/dependency&gt;<br>  &lt;dependency&gt;<br>   &lt;groupId&gt;net.java.dev.jna&lt;/groupId&gt;<br>   &lt;artifactId&gt;jna&lt;/artifactId&gt;<br>   &lt;version&gt;5.13.0&lt;/version&gt;<br>  &lt;/dependency&gt;<br>  &lt;!-- https://mvnrepository.com/artifact/io.cucumber/cucumber-testng --&gt;<br>  &lt;dependency&gt;<br>   &lt;groupId&gt;io.cucumber&lt;/groupId&gt;<br>   &lt;artifactId&gt;cucumber-testng&lt;/artifactId&gt;<br>   &lt;version&gt;7.33.0&lt;/version&gt;<br>  &lt;/dependency&gt;<br><br>  &lt;dependency&gt;<br>   &lt;groupId&gt;net.java.dev.jna&lt;/groupId&gt;<br>   &lt;artifactId&gt;jna-platform&lt;/artifactId&gt;<br>   &lt;version&gt;5.13.0&lt;/version&gt;<br>  &lt;/dependency&gt;<br>  &lt;!-- Extent Reports --&gt;<br>  &lt;dependency&gt;<br>   &lt;groupId&gt;com.aventstack&lt;/groupId&gt;<br>   &lt;artifactId&gt;extentreports&lt;/artifactId&gt;<br>   &lt;version&gt;5.1.2&lt;/version&gt;<br>  &lt;/dependency&gt;<br>  &lt;!-- Extent Cucumber 7 Adapter --&gt;<br>  &lt;dependency&gt;<br>   &lt;groupId&gt;tech.grasshopper&lt;/groupId&gt;<br>   &lt;artifactId&gt;extentreports-cucumber7-adapter&lt;/artifactId&gt;<br>   &lt;version&gt;1.14.0&lt;/version&gt;<br>   &lt;scope&gt;test&lt;/scope&gt;<br>  &lt;/dependency&gt;<br>  &lt;!-- https://mvnrepository.com/artifact/io.cucumber/cucumber-java --&gt;<br>  &lt;dependency&gt;<br>   &lt;groupId&gt;io.cucumber&lt;/groupId&gt;<br>   &lt;artifactId&gt;cucumber-java&lt;/artifactId&gt;<br>   &lt;version&gt;7.33.0&lt;/version&gt;<br>  &lt;/dependency&gt;<br><br><br> &lt;/dependencies&gt;<br>&lt;/project&gt;</pre><p>I have now created a very simple TestNG framework, as we have two desktop applications and need to trigger both using a single method.</p><p>In my project, I required two drivers: one for <strong>WinAppDriver </strong>to handle windows based scenarios and another for <strong>ChromeDriver</strong> to handle web application scenarios.</p><pre>public void setUp() throws Exception {<br><br>  try {<br>   new ProcessBuilder(applicationPath).start();<br>   System.out.println(&quot;Launching application...&quot;);<br>   Thread.sleep(5000);<br>  } catch (Exception e) {<br>   throw new RuntimeException(&quot;❌ Could not launch application.exe&quot;, e);<br>  }<br><br>  CommonMethodsForResPOS temp = new CommonMethodsForApplication(null);<br><br>  String windowHandle = temp.getWindowHandleHex(&quot;ApplicationhandleName&quot;);<br>  if (windowHandle == null || windowHandle.isEmpty()) {<br>   throw new RuntimeException(&quot;❌ Could not find MainWindowHandle for Application&quot;);<br>  }<br><br>  DesiredCapabilities caps = new DesiredCapabilities();<br>  caps.setCapability(&quot;appTopLevelWindow&quot;, &quot;0x&quot; + windowHandle);<br>  caps.setCapability(&quot;platformName&quot;, &quot;Windows&quot;);<br>  caps.setCapability(&quot;deviceName&quot;, &quot;WindowsPC&quot;);<br><br>  driver = new WindowsDriver(new URL(&quot;http://127.0.0.1:4723&quot;), caps);<br>  driver.manage().timeouts().implicitlyWait(10, TimeUnit.SECONDS);<br>  System.out.println(&quot;✅ Attached to RestaurantPOS (Handle: 0x&quot; + windowHandle + &quot;)&quot;);<br> }</pre><p>In the above code, a Windows-based application is initialized, after which the automation tests suite will be executed.</p><p>Below are the steps for one automation test. Based on the feature file, we need to create step definitions and link them with the corresponding Gherkin steps.</p><pre>Feature: eCube ResPos AutomationTests<br><br>  Scenario: Settle order through Selection view<br>    Given the user is launching the desktop application<br>    When the user logs into the resPos application<br>    Then the user selects an outlet and room number in a club<br>    When the user enters the member code in the application<br>    Then the user adds products into the cart through the Selection view</pre><p>Now that we have already launched the desktop application using the setUp() method, the next step — according to the steps above — is to log in to the application. After a successful login, we can perform other operations such as selecting an outlet and choosing a room number for a member.</p><p>In a web application, we know how to handle multiple windows using Selenium. When a user clicks on a link that opens in a new window, we need to iterate through all the opened windows, switch to the correct one, and then perform the subsequent operations. The same scenario occurs in a Windows application, but with a major twist in how it is handled. We first retrieve the <strong>applicationID</strong> of all running applications and then drill down to identify which handle belongs to our application. Once the correct application handle is identified, we fetch all window handles associated with that application, switch to the required window, and perform the necessary operations.</p><p>When the application starts, first capture all window handles. This approach helps avoid confusion with active window handles, allowing you to accurately identify the correct window handle ID and switch to it.</p><p>First, identify the correct window handle ID and switch to it.</p><p>Below is the approach to handle window handles and switch to the desired window. Here, I am checking that the number of window handles is greater than one. This is important because if it is not, the new window may not have been generated or its ID may not be active yet. Handle this scenario by implementing an explicit wait. Wait until the number of window handles is greater than one, ensuring that the new window is fully generated and its handle is active before switching to it.</p><pre>WebDriverWait wait = new WebDriverWait(driver, 10);<br>  wait.until(d -&gt; driver.getWindowHandles().size() &gt; 1);<br><br>  Set&lt;String&gt; allWindows = driver.getWindowHandles();<br>  for (String handle : allWindows) {<br>   if (!handle.equals(parentWindow)) {<br>    driver.switchTo().window(handle);<br>    // System.out.println(&quot;✅ Switched to Member Card Validation dialog&quot;);<br>    break;<br>   }<br>  }</pre><p>In a Windows-based application, finding a unique locator can be a tricky task. However, once you become familiar with it, you will definitely enjoy working with it. I have already discussed how to fetch locators in a Windows-based application. Please find below some of the XPaths used in my application. In a Windows application, we need to ensure that the locators are unique or we need to make unique. One drawback of automation of Windows-based applications is that we don’t have access to the complete DOM at once, unlike in web applications. We need to drill down into the application to locate and identify unique locators.</p><pre>WebElement openWindowPopupOpenButton = session.findElementByXPath(&quot;//Button[@Name=&#39;Open&#39;][@AutomationId=&#39;1&#39;]&quot;);<br>          openWindowPopupOpenButton.click();<br><br>By usernameField = By.xpath(&quot;//*[contains(@AutomationId, &#39;txtUserName&#39;)]&quot;);<br>private By memberCodeTextBoxLocator = MobileBy.AccessibilityId(&quot;txtMemberCodeCardId&quot;)</pre><blockquote><em>How is data implemented in the framework?</em></blockquote><p>I am using JSON files to drive data in my framework, as they are easy to handle. I create the necessary data and store it in JSON files, which I then use while verifying reports with the admin. I have also used the Page Object Model pattern, as well as Page Factory, in the framework, depending on the specific requirements.</p><blockquote>Experience with Automation</blockquote><p>When planning for automation, we generally make sure that we don’t get “stuck in the elevator” once we start. This is important because it can be very challenging to recover and move forward if we encounter blockers later.</p><p>We faced many challenges and blockers initially, mainly because we were new to the tool. However, if the team is confident and management is willing to invest time and resources, we can discover new ways to achieve</p><p>our goals. These challenges could include tool limitations, lack of resources, the learning curve, or time-consuming tasks. Most management teams often underestimate manual tests and also the amount of work that test automation requires, especially if they expect everything to be fully automated. This can lead to excessive maintenance effort and ultimately reduce the overall added value of automation. Once you choose the right tool, resource selection should be based on the tool and, more importantly, the type of scripts you plan to write for the project. Focus on identifying which tests should remain manual and which can be automated, then define a manageable percentage of automation. This approach ensures a more practical and efficient automation strategy. This approach will lead to a higher ROI for your automation project, which is exactly what management expects. Therefore, it is important to communicate this clearly from the start.</p><ul><li><strong>Environment Stability</strong>: Ensuring that the test environment mirrors the production environment and is stable can be an ongoing challenge.</li><li><strong>Maintenance Overhead</strong>: As the application evolves, test scripts often require frequent updates. This can become quite labor-intensive, especially if the test suite is extensive.</li><li><strong>Changes in Requirements</strong>: Rapid changes in project requirements can lead to instability and require continuous updates to the test scripts, making it challenging to maintain a robust test automation framework.</li></ul><p>Feel free to share your feedback and insights about the blog in the comments below. I would also like to hear your thoughts and experiences on automation, WinAppDriver, and your overall experience with similar tools.</p><p>Wait!!! Hit the claps is a good idea to start positive thinking!!!!</p><blockquote><strong>#MustRead</strong></blockquote><p><a href="https://kishor-munot.medium.com/debate-topic-javascript-vs-typescript-2914298b2578">Debate Topic: JavaScript vs TypeScript | Medium</a></p><p><a href="https://kishor-munot.medium.com/speed-and-performance-lighthouse-with-cypress-part-1-2243405980ed">Speed and Performance : LightHouse with Cypress : Part -1</a></p><p><a href="https://kishor-munot.medium.com/cypress-14-with-lighthouse-part-2-2ff498875034">Cypress 14 and 15 with LightHouse</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/914/0*BPBJIY-gchFKgXMC" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8391f1273c7a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>