How do you handle stories that aren't completed in a sprint

[Pete Jenkins]

I have been on a project for a while and our sprints don't appear to be going as well as we like. Our stories are pointed with dev and testing in mind. However throughout the sprint we are repeatedly seeing development effort completed but testing holding up the story from getting completed. The recommendation is that we carry over our stories into the next sprint and repoint to accommodate just the testing effort. We end up not getting credit for any or much of the development work on stories that carry over. My thought is if we create sub tasks for development and testing we can complete our development tasks and get credit during that sprint and testing tasks can carry over. Granted the story wouldn't be complete but at least our velocity would not be skewed. Is this the right approach? Does anyone else have a suggestion? 

[Michael Andolfatto]

Hi @Pete Jenkins , welcome to the Community!

What you're writing sounds a bit contradictory to me- you're sizing your issues with development and testing in mind (correct) but are consistently unable to deliver due to not being able to complete testing within your sprint? It sounds like you need to increase the padding on your estimates to ensure testing can be completed, is there a reason this is not being done?