And just a note...as mentioned in one of your other requests, we don't use recording to record a full test. We manually construct our keyword tests, using recording only when necessary to "discover" certain workflows.
It's a mindset of viewing test automation less like just recording tests you're doing manually and more like software development, which is what test automation is. It's developing software to test other software. So, there is methodology and such that goes along with it. Think of the object identification/namemapping as the development of the UI of an application under test and the actual test "code" itself as the code behind the UI that performs the functions. Both take care, attention, and methodical practice to do well.
Related Content
- 12 years ago
- 11 years ago