In my current job, and in several of my past jobs, a significant portion of my time (say, as much as 20%) is finding inconsistencies/typos in the interface, noting and logging them, and tracking crashes and runtime errors and what I did to produce them. (In my current job, they've decided to use my method of error logging in their fix cases now!) An example of finding a typo in an interface would be noting and logging an incorrect apostrophe usage in a menu item ("Copy another suppliers' setup"), or finding an inconsistency would be noting that some fields refer to an item by one term and other fields refer to the same item by another term (in the current application, we're having a persistent problem with switching the term "Dealer" over to "Ship To" and standardising the abbreviation for "Purchase Order" to "PO" not "P.O." or "Po." (Incidentally, I've seen the abbreviation used both the two former ways on the same tab in the application.)
Is this normal tech-writing kind of stuff (once a copy-editor, always a pain in the ass), or have I really and truly crossed over into testing (or what)?
Incidentally, this is why I think there should be a separate job title for someone who copy-edits the text in a UI.