Scrum and testing. How does scrum testing work in practice?

Question

Software testing

In Scrum, the success of a sprint is all the tasks that were added to scrum that ended up in the Done status.
But what if the developers do tasks until the very last day of the sprint? When will testing take place?
If there are fewer tasks in the sprint to give some margin for testing, then what will the developers do?

Answer 1

A whole book is devoted to this topic: "Agile Testing. A Practical Guide for Software Testers and Agile Teams" by the authors: Lisa Crispin, Janet Gregory.
It describes very well the role of testers and developers (in terms of testing), how best to build a process, what to pay attention to, etc.
The short answer to the original question is that it is necessary to distribute the work in the team in such a way that everyone is actively involved in the development/testing process during the sprint. The whole team is responsible for the result, so leaving half a day to test the raw code is just to hammer the bolt on quality.

Answer 2

AFAIK (as a former certified scrum master) there is no "success" or "failure" sprint. Sprint is a timebox for work. If you made a mistake in planning, then in retrospect you need to understand and fix how to avoid the same rake in the next planning.
Status Done vs Testing depends on what you have in your Definition of Done. It happens that the tester is part of the team and testing is just his usual tasks.
If testing comes with a lag, then it’s easier to fix the bug as a separate task in one of the next sprints than to switch the maiden. The fact that the complete closure of the "user story" takes several sprints is quite normal.

Answer 3

then what to do with developers?

Naturally, the tasks of the next sprint and the tasks that are transferred from this sprint to the next one.
Well, fixing bugs, of course.