> ## Documentation Index
> Fetch the complete documentation index at: https://help.loopiq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Use the Page Object Capture Chrome Extension

## What this does

The LoopIQ Page Object Capture Chrome extension captures meaningful UI objects from an application page and stores approved objects in a LoopIQ Page Object Repository.

Use it to:

* capture multiple application pages into one repository
* capture visible controls and interaction-revealed modal content
* review, rename, or remove objects before upload
* version page objects as the application changes
* reuse objects in Playwright and Selenium generation

Capture is always initiated and approved by the user.

## Before you start

You need:

* an active LoopIQ browser session
* access to `Test Management` and `Test Automation`
* permission to use Page Object Repositories
* the extension installed in the same Chrome profile as your LoopIQ session
* an application or module selected in LoopIQ
* an active Page Object Capture session

The extension obtains the organization, capture token, repository options, and approved origin from the active LoopIQ session. Users should not manually enter organization IDs or capture tokens during normal use.

## Install the extension

1. Build or obtain the approved extension distribution.
2. Open `chrome://extensions`.
3. Enable `Developer mode` when installing an unpacked development build.
4. Select `Load unpacked`.
5. Choose the extension's `dist` folder.
6. Pin `LoopIQ Capture` to the Chrome toolbar.

After updating the extension, return to `chrome://extensions` and select `Reload` for the LoopIQ extension.

Organizations distributing the extension through managed Chrome policy or the Chrome Web Store should follow their administrator's installation instructions.

## Start capture from LoopIQ

1. Sign in to LoopIQ in Chrome.
2. Open `Test Management`.
3. Select `Test Automation`.
4. Select the application and optional module.
5. Choose or create a Page Object Repository.
6. Start the Page Object Capture session.
7. Navigate to an approved page in the target application.
8. Open the LoopIQ extension.

The extension opens in a separate scrollable popup so all context, capture, review, and submission controls remain accessible.

If the extension reports `No active LoopIQ capture session`, return to LoopIQ and start a new capture session. Confirm that LoopIQ and the extension use the same Chrome profile.

## Choose or create a repository

The `Page Object Repository` field is searchable.

1. Enter part of the repository name.
2. Select a matching repository.
3. If no suitable repository exists, create one from the LoopIQ Test Automation page.

An application or module can have multiple repositories. Each repository can contain multiple captured pages and immutable versions.

Use a clear name that describes the product area, such as:

* `Customer Portal`
* `Admin Console`
* `Checkout and Billing`

Do not create a separate repository for every page unless those pages have separate ownership or lifecycle requirements. Use pages within a repository for individual routes or screens.

## Capture a page

1. Open the target application page.
2. Open `LoopIQ Capture`.
3. Confirm the application, module, repository, and approved origin.
4. Select `Capture page objects`.
5. Review the captured objects.
6. Rename unclear objects.
7. Remove low-value or unwanted objects.
8. Select `Approve and send to LoopIQ`.

Saving another application route to the same repository creates or updates that repository page and creates a new repository version.

## What the extension captures

The extension looks for meaningful automation and semantic content, including:

* the document page title
* headings
* buttons and links
* form inputs, selects, and text areas
* tabs, menu items, navigation controls, and status elements
* dialogs and modal content
* meaningful paragraphs and text-bearing containers
* elements with accessible labels, roles, or stable test attributes
* hidden or currently undisplayed modal controls that may appear after a user action

Hidden captured objects are marked `hidden until interaction` in the review list.

The extension may inspect hidden semantic dialog content so future interactions can use objects that appear after opening a menu, modal, drawer, or conditional form. It does not execute those interactions automatically during capture.

## What the extension excludes

The extension is designed not to capture:

* password fields
* HTML hidden inputs
* current user-entered field values
* tokens, secrets, API keys, or credentials
* tracking pixels
* decorative elements without testing value
* duplicate layout wrappers
* oversized or low-value text containers

LoopIQ applies backend validation before accepting uploaded objects. An unsafe or unsupported capture can be rejected even after local review.

## Rename a captured object

Use a name that describes the object's purpose rather than only its appearance.

1. Find the object in the review list.
2. Edit `Object name`.
3. Enter a concise semantic name, such as `Submit order`, `Customer email`, or `Open approval dialog`.
4. Continue reviewing before submission.

Renaming changes the object name sent to LoopIQ. It does not alter the source application.

## Remove a captured object

1. Find the unwanted object in the review list.
2. Select `Remove`.
3. Confirm it no longer appears in the pending capture.

Removal applies to the current review before upload. It does not delete an object from an older immutable repository version.

To remove an already stored object, make a new approved capture or manage the repository in LoopIQ so the change is recorded in a new version.

## Manage multiple pages

Repeat capture for each page that belongs in the repository.

In LoopIQ you can:

* rename pages
* archive or restore pages
* reorder pages
* inspect page object counts
* use pages in cross-page journeys

Archive obsolete pages instead of reusing their names for unrelated screens. A page used by an active journey must be removed from or replaced in the journey before archival.

## Review repository history

Each approved capture creates an immutable repository version.

Use `Version history` to:

* compare the latest and previous versions
* identify added or removed objects
* review locator, attribute, state, and semantic changes
* restore a known-good version

The visual compare drawer highlights field-level changes before restore. Restoring creates another immutable version and records an audit event; it does not overwrite history.

## Use captured objects in automation

1. Open `Test Management`.
2. Select `Test Automation`.
3. Choose the application, module, and framework.
4. Select the Page Object Repository.
5. Optionally select a cross-page journey.
6. Select a source work item in `Requirement or test intent`.
7. Select `Generate manual + automated tests`.
8. Review the generated package before selecting `Approve and create`.

Captured page objects can be used by Playwright and Selenium generation. Karate API tests do not require browser page objects.

## Troubleshooting

### No active capture session

* Confirm you are signed in to LoopIQ in the same Chrome profile.
* Open Test Automation and start capture again.
* Refresh the LoopIQ page.
* Close and reopen the extension popup.
* Confirm the extension has access to `https://app.loopiq.com`.

### Repository search returns no matches

* Confirm the correct application and module are selected.
* Enter fewer characters.
* Confirm the repository is active.
* Refresh the capture session after creating a repository.
* Confirm your selected team has access to the repository.

### Capture is rejected with 404

* Reload the latest extension build.
* Confirm the production API exposes the Page Object Capture routes.
* Start a new session so the extension receives the current upload path.
* Ask an administrator to verify the gateway route and backend deployment.

### Capture is rejected by validation

* Remove unsupported or low-value objects.
* Confirm object names do not contain secret-like values.
* Confirm the page origin matches the approved origin.
* Confirm the capture token has not expired.

### A modal object is missing

* Open the modal or conditional interface and capture again.
* Confirm the object has meaningful text, an accessible role, label, or stable test attribute.
* Review hidden objects marked `hidden until interaction`.
* Avoid capturing framework-generated containers that have no semantic content.

### Too many objects are captured

* Remove unwanted objects in the review list.
* Capture one route or workflow page at a time.
* Keep meaningful controls and text needed for assertions.
* Prefer stable accessible labels or test attributes.

## Recommended practices

* Start every capture from LoopIQ so organization and repository context are trusted.
* Capture pages in a controlled test environment.
* Review and approve every object before upload.
* Rename objects using business-readable names.
* Remove decorative or unstable objects.
* Keep related pages in one repository and model end-to-end flows as journeys.
* Compare versions before restoring.
* Never intentionally capture production secrets or personal data.