---
title: "Move a prepared file between folders"
description: "Verify that moving an existing test file changes folder membership exactly once and preserves the file detail and preview identity."
canonical_url: "https://vostride.com/agent-library/files-media/folder-move-membership.md"
md_url: "https://vostride.com/agent-library/files-media/folder-move-membership.md"
content_kind: "recipe"
topic: "files-media"
---

# Move a prepared file between folders

Verify that moving an existing test file changes folder membership exactly once and preserves the file detail and preview identity.

## Risk

A move dialog can report success while leaving a ghost entry in the source or creating a second record in the destination. Inspect both folders and the stable file identity after the move.

## Fixtures

- The QA library has empty folders Incoming QA and Reviewed QA, both owned by the test account.
- Incoming QA contains one prepared document named Inspection checklist with a known asset key and visible CHECKLIST FIXTURE heading.
- The application contract defines Move as changing the parent folder rather than copying the file.

## Steps

1. Open Incoming QA and verify Inspection checklist is its only file, then open the preview and confirm the fixture heading.
2. Choose Move, select Reviewed QA, and confirm the move through the normal application dialog.
3. Verify Incoming QA becomes empty after returning to its folder listing.
4. Open Reviewed QA and verify exactly one Inspection checklist entry appears.
5. Open the moved entry, verify the same asset key and fixture heading, then reload the destination folder and verify membership persists.

## Expected results

- The source folder contains zero references to the moved file after completion.
- The destination contains one reference to the original asset identifier.
- The file preview remains usable and shows unchanged prepared content after its parent folder changes.

## False-pass traps

- A destination entry alone cannot distinguish move from copy.
- A stale source listing may look empty because a search remains active; clear unrelated filters before checking membership.

## Cleanup

- Move the fixture back to Incoming QA or delete the document and both temporary folders.

## 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)

- [Files and media QA recipes](/agent-library/files-media.md)
- [Software factory QA library](/agent-library.md)