They aren't the same job, regardless for how similiar the titles are.
My point was the skills required in architecting a solution vs testing a given specific solution differ. So, while you can more easily fall/move into a automated testing role, it's harder to do so into a core programming job. The bar for moving into the latter, rightly or not, very much higher.
Working in a non-development group doesn't somehow make you not a software developer.