Skip to main content
deleted 15 characters in body
Source Link
alecxe
  • 11.4k
  • 11
  • 51
  • 107

Welcome to SQA poc,

Many people's first encounter with automation is to start with a record and playback tool. You quickly learn the limitations of that method because the code it produces is crude and not very maintainable. I

I do know some people who continue to use a recorder only for the purpose of getting the ID's or other unique identifiers, however there is still a manual process to take the ID's from the generated code and insert it into your own code. In

In my experience, every browser now has very good built in developer tools that make inspecting an element and finding a unique identifier pretty simple. I would suggest staying away from recorders as it would likely complicate your process instead of simplify it.

Welcome to SQA poc,

Many people's first encounter with automation is to start with a record and playback tool. You quickly learn the limitations of that method because the code it produces is crude and not very maintainable. I do know some people who continue to use a recorder only for the purpose of getting the ID's or other unique identifiers, however there is still a manual process to take the ID's from the generated code and insert it into your own code. In my experience, every browser now has very good built in developer tools that make inspecting an element and finding a unique identifier pretty simple. I would suggest staying away from recorders as it would likely complicate your process instead of simplify it.

Many people's first encounter with automation is to start with a record and playback tool. You quickly learn the limitations of that method because the code it produces is crude and not very maintainable.

I do know some people who continue to use a recorder only for the purpose of getting the ID's or other unique identifiers, however there is still a manual process to take the ID's from the generated code and insert it into your own code.

In my experience, every browser now has very good built in developer tools that make inspecting an element and finding a unique identifier pretty simple. I would suggest staying away from recorders as it would likely complicate your process instead of simplify it.

Source Link
Sam Woods
  • 8.6k
  • 25
  • 43

Welcome to SQA poc,

Many people's first encounter with automation is to start with a record and playback tool. You quickly learn the limitations of that method because the code it produces is crude and not very maintainable. I do know some people who continue to use a recorder only for the purpose of getting the ID's or other unique identifiers, however there is still a manual process to take the ID's from the generated code and insert it into your own code. In my experience, every browser now has very good built in developer tools that make inspecting an element and finding a unique identifier pretty simple. I would suggest staying away from recorders as it would likely complicate your process instead of simplify it.