V4 Prathirupa

# V4 Prathirupa V4 Prathirupa is a Chrome and Chromium-based browser extension for web resilience testing, API inspection, and controlled response mocking. It allows developers, QA engineers, automation specialists, and application support teams to observe network traffic generated by selected websites, inspect the requests and responses in detail, save representative calls, and replace future responses with configurable mock data. The extension is designed for testing conditions that are difficult or time-consuming to reproduce with a real backend, such as API errors, empty responses, unusual payloads, service outages, and specific response statuses. A tester can capture a real API call, convert it into a mock rule, and replay a controlled response directly in the browser. V4 Prathirupa works as a local testing tool. It does not require a separate proxy server, backend service, hosted dashboard, or external data platform. Website configuration, captured calls, and mock rules are managed by the extension and stored locally in the browser environment. ## Main Purpose The extension brings API recording and response mocking into the browser where the application is already running. A typical workflow begins with adding a website to the extension, granting the required host permission, and enabling recording for that website. Once recording is active, the extension observes network activity from matching browser tabs. The tester can then use the website normally, navigate through screens, submit forms, open pages, or trigger the specific workflow they want to inspect. After network activity has been captured, the tester opens the V4 Prathirupa workspace. The workspace presents the captured API calls in a searchable, sortable table. Each call can be inspected to understand its method, URL, resource type, status, initiator, size, timing, headers, request body, and response body. A captured call can also become the starting point for a mock rule. V4 Prathirupa pre-fills the rule with information from the real request, including the HTTP method, exact URL, response status, response headers, and response body. The tester can then adjust the values to represent the desired test condition. For example, a successful `200` response can be changed to a `503` service-unavailable response, or a normal JSON payload can be replaced with an empty list, malformed business data, a permission error, or a custom fixture. Once the rule is enabled, matching requests from the selected website can receive the configured response instead of the real response. This makes it possible to test frontend behavior repeatedly and consistently without modifying the production-like service behind the application. ## Popup Control Center The extension popup is the primary control surface for configuring monitored websites and controlling recording activity. It is intentionally focused on operational actions rather than detailed data analysis. Users can add a website in two ways. The first option is to add the active browser tab. This is useful when the tester is already viewing the application they want to inspect. The extension reads the active tab's URL, determines its origin, and requests the necessary host permission. The second option is to enter a website manually, such as `app.example.com` or a complete URL such as `https://app.example.com`. Only regular HTTP and HTTPS websites can be monitored. Browser-internal pages and protected browser contexts, including pages such as `chrome://extensions`, extension pages, DevTools pages, local browser pages, and similar internal URLs, are rejected. This prevents the extension from attempting to attach to pages that cannot or should not be inspected. Adding a website does not automatically begin recording. This separation gives users explicit control over when the debugger is attached and when traffic collection starts. Each configured website appears in the popup with its current state, allowing users to see which websites are available and which ones are actively recording. The popup supports selecting multiple websites and starting or stopping recording in bulk. A user can choose several monitored origins and start recording for all eligible selections at once. Recording can later be stopped for selected websites without removing their configuration or deleting their captured data. A monitored website can also be removed. Removing a website is treated as a complete cleanup action for that website: its recording and mocking attachments are detached, its captured calls are deleted, its saved mock rules are deleted, and its references are removed from the extension settings. This prevents stale identifiers from remaining behind if the same origin is added again later. ## Global Active and Paused State V4 Prathirupa includes a global toggle that controls recording and mocking across the entire extension. The toggle provides a fast way to suspend all active behavior while preserving the user's configuration. When the extension is active, eligible recording sessions can observe traffic and enabled mock rules can intercept matching requests. When the extension is paused, no requests are recorded and enabled mock rules do not replace responses. Website configuration, saved API captures, selected websites, and mock rules remain stored. Pausing also disables mutation-oriented controls that could otherwise change the testing state while the extension is suspended. Workspace actions that create, edit, enable, disable, or delete rules are unavailable during the paused state, and open mock editors are closed. This creates a clear boundary between an active testing session and a temporarily suspended one. Resuming the extension restores the active runtime state. The extension preserves the user's recording intent, so websites that were configured for recording can be attached again when the global toggle is turned back on. The background service worker also rehydrates act…