---
title: "Apply a bulk action to explicit cross-page selections"
description: "Verify that selecting specific rows on two pages affects exactly those records and makes the selection scope visible before the bulk action."
canonical_url: "https://vostride.com/agent-library/data-tables/selection-across-pages.md"
md_url: "https://vostride.com/agent-library/data-tables/selection-across-pages.md"
content_kind: "recipe"
topic: "data-tables"
---

# Apply a bulk action to explicit cross-page selections

Verify that selecting specific rows on two pages affects exactly those records and makes the selection scope visible before the bulk action.

## Risk

Bulk selection often confuses the current page with the full dataset. This recipe selects named records individually, avoiding assumptions about a Select all control whose semantics may differ.

## Fixtures

- A test table contains twelve tasks across two pages, each with a known key and initial status Open.
- The intended selected set is Task 02 on page one and Task 11 on page two.
- A prepared read-only state check reports all twelve statuses independently of the current page.

## Steps

1. Open page one, select Task 02 by its checkbox, and verify the selection count is one.
2. Go to page two, select Task 11, and verify the selection summary reports two selected records.
3. Choose the reversible bulk status action and verify any confirmation indicates the two-record scope before applying Done.
4. Verify Task 11 is Done, return to page one, and verify Task 02 is Done.
5. Run the prepared all-record check and verify the other ten tasks remain Open, then reload the table and confirm the two changes persist.

## Expected results

- The changed identifier set equals exactly Task 02 and Task 11.
- The selection summary survives pagination and accurately reports the intended two-record scope.
- All unselected records retain their original status according to the independent full-dataset check.

## False-pass traps

- Checking only the visible page can miss an accidental bulk update on the other page.
- A selection count of two does not prove which two rows are selected; verify names or keys before committing.

## Cleanup

- Restore both task statuses and delete all twelve fixtures if the table is disposable.

## Use with agent-qa

Adapt this test design to your application's acceptance criteria and configured target using the [recipe execution guide](/agent-library/software-factory/turn-a-recipe-into-an-agent-qa-test.md). External fixture setup and non-UI checks require your own supported hooks or test tooling. Validate the authored test, execute it, and inspect the completed evidence; this recipe is not a recorded test result.

## References

- [agent-qa test](/docs/agent-qa/configuration/test.md)
- [agent-qa first test](/docs/agent-qa/guides/first-test.md)
- [agent-qa web testing](/docs/agent-qa/guides/web-testing.md)

- [Data table QA recipes](/agent-library/data-tables.md)
- [Software factory QA library](/agent-library.md)