For each User Story in the sprint, a label should be added:

AutomationRequired
AutomationNotRequired
TestingNotRequired

A task should be added for:

each test that the test team believes needs to be done,
you may also create tasks for analysis,
manual testing
any/all test activity should be captured in tasks!

Task states should then be managed as you work on them, New → Active → Resolved, please see /wiki/spaces/RedboxHome/pages/2562777477.

Once all the tasks of a story are complete the story can be moved to Done (assuming it has gone through the pre-req states /wiki/spaces/RedboxHome/pages/2562763114)

If there are testing tasks open at the end of the sprint, and therefore the the story is not 'Done' then it will be copied forward to the next sprint.

Story is Already Done

If a user story has been marked as Done already, which won't normally be the case, then we have two options.

In Sprint

Move the story back to ready for test.
Check the story Area and iteration path
Add required tasks
Progress task and story management as usual

Story completed in previous sprint

Ignore the existing story and create a new story with appropriate
Ensure details and acceptance criteria are are set. The story should be discrete and have a known end point.
Add story point estimate for effort
Set Area, Iteration correctly
Create tasks for each test.