As a manual tester, I have to be able to uniquely identify the elements on the page and what I want to do to them (check them, click them, select them, etc.). I should be able to figure out WHAT I want to do regardless of how easy (or hard) it is to identify the elements. HOW I do it would require me to have helpful locators. Can you add identifier to the code? If the code is not testable then as a developer I have not done a very good job. By making the code testable getting it to production is easier. If as a developer my goal is to get code to QA then I need to redefine my goals. Until my code is in production and people are using it, I am not done. If writing testable code makes my code making to production faster than I am going to write testable code.
Now this is what I push for. If you do not have the luxury of doing quality assurance and you are REALLY doing quality control then you'll just have to spot the patterns and find unique, static locators to find the elements you need to interact with. There is no magic solution in this case. You just have to be good at working in a difficult situation.