Should a dev task in a sprint have a separate test task or can testing be documented and managed on the development task?

Question

Should a dev task in a sprint have a separate test task or can testing be documented and managed on the development task?

I am new to the devops product and I am trying to find the optimal way to handle the movement of testing for a dev task across the scrum board.

Option 1) Create a separate QA task for every dev task. CONS: extra overhead - creating additional tasks, focusing on more tasks on the board. PROS: ? What are they?
Option 2) Passing a dev task through a QA state assigned to a QA person, who documents finding on the same task, progressing it either backwards or forwards depending on test results. PROS: Less overhead, less clutter on the board, better clarity of the state. CONS: None that I can think of

Thanks you. Coming fronm a Jira background I am struggling a wee bit with Devops.

Tim

Answer 1

Devops / TFS is not currently supported here on Q&A. The product group for Azure DevOps / TFS actively monitors questions over at
https://developercommunity.visualstudio.com/report?space=21&entry=problem
https://developercommunity.visualstudio.com/report?space=22&entry=problem

--please don't forget to upvote and Accept as answer if the reply is helpful--