The key question goes back to estimation of User Stories.
I believe that combining testing and development Story Points in one Jira user story as separate tasks doesn’t make sense, as it is like combining apples and oranges.
Specifically it doesn’t allow proper estimation of Velocity. Assume the engineering team finished big task on Friday 5pm - obviously it won’t get tested until next week and the development SP won’t be accounted in the sprint - JIRA doesn’t count SP until the Story is moved to done - thus development SPs won’t be counted and dashboards and charts will be way off.
I already foresee a bunch of comments re: automated testing, etc. In my experience, it doesn’t work - still, tasks cannot be fully developed and tested in one sprint.
As of now I’m separating Q/A from development - points count once development is completed, but this approach also doesn’t feel right.