If a Scrum "increment" is to be "done" by the end of the "sprint", where "done" means usable/releaseable, I assume testing has to be part of the sprint. Since sprints are not supposed to last more than a month, depending on the scope of the sprint goals, testing is either ongoing or occurs just before the end of the sprint. It seems on-going has to be the answer, but regressive testing of the new increment with previous incrments can grow into an increasing work item.
Does anyone with experience in this have thoughts to share so I can understand better how this is done?
I think there are a lot of variables that need to be considered with your question, but if you are working in DevOps or agile, testing would be ongoing. As far as who is responsible, it's important the entire team is dedicated to quality. As far as regression testing, there is probably a lot of automated testing you can introduce to reduce the manual testing work load.
My experience with testing is minimal, but there are a lot of great practioners and experts on our TechWell Hub Slack workspace. I'm sure if you drop this question in one of the channels there, you'll get feedback from people a lot more experienced than me! You can join at hub.techwell.com.
StickyMinds is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.