My team follows test driven development, and sometimes extreme programming.
If the latter, they would often complete a user story without testing, and then write the tests afterwards.
So, if I have a Trello card and the Trello card is:
"Write tests for the API"
That is not a user story i.e. "As a user, I want , so that...."
but never the less the story related to that is completed (the functionality), where this was not done at the time due to time constraints. Currently I just write a Trello card like that, and put it in the sprint which contains a lot of user stories. Is this the correct approach?