Per-file progress and batch-summary evidence

Review batch upload progress when only some files finish

Show per-file states alongside the overall summary so a partial failure does not disappear behind a completion message.

  • ✓Complete hides an incomplete item
  • ✓Progress loses file identity
  • ✓Retry appears to restart everything

A focused report for incomplete batches and retries

Individual outcomes retained

Keep each synthetic filename connected to its success, failure, or pending state.

Aggregate wording checked

Compare the batch message with the rows it is supposed to summarize.

Retry scope explicit

Agree whether retry targets one failed file before handing off the issue.

Review a mixed outcome, not a perfect batch

A customer adds several harmless attachments to your application. Most finish, one fails under a controlled test condition, and the dialog announces Upload complete. Review whether the overall message explains the individual outcomes and leaves a clear next action for the failed file. This scenario concerns your application's batch uploader, not a claim about batch processing features or arbitrary file support in Retick.

Make each fixture recognizable

Use approved synthetic files with distinct short names and known expected outcomes. Record selection, progress changes, the controlled failure, the settled summary, and retrying that file. Note browser, build, fixture sizes, viewport, and the method used to stage failure. Avoid personal filenames, local paths, and document contents. Capture with the supported browser extension or upload authorized video that retains enough time to understand the status transitions.

Report disagreement between row and summary

An example issue is Batch completion message hides a failed attachment. Inspect Retick's AI candidate findings and annotate the failed row beside the overall message. Edit any claim that a file was lost unless the destination has been checked separately. A misleading aggregate status, a missing row-level retry, and a duplicate after retry are different findings. Reject generated throughput estimates that the recording cannot substantiate.

Example acceptance criteria

After the controlled mixed result settles, each synthetic file should have an understandable outcome and the batch summary should acknowledge the incomplete item. Retrying the failed row should target that file without restarting successful rows, if that is the approved product behavior. Completion should reflect the revised outcomes. Verify the destination list directly and check that filenames still identify the corresponding rows when progress indicators disappear.

Compare repeated and interrupted attempts

Use a review cycle for initial, mixed, and retried states. Follow up with cancelling one pending file, closing and reopening the progress view where supported, and retrying after another controlled failure. Download reviewed issues or create cards from selected findings on an individual media item in Trello. Retick does not execute uploads for your application, verify file integrity, or measure transfer performance. The application team needs separate checks for those behaviors; the visual review explains whether progress and outcomes are communicated consistently.

Make partial upload outcomes visible

Capture a controlled mixed batch and review the failed file's next action.