I am working on a new project and I wanted to know which automation tool is the best to use. Should I record-play or code?
相关问题
- Selecting an item from a combo box selenium driver
- MongoError: pool is draining, new operations prohi
- How to use VBA or Powershell to export lists from
- Run unit tests on git push and integration tests o
- How to trigger a click on a chrome extension butto
相关文章
- How to replace Middleware in integration tests pro
- Preventing truncation of long strings in pytest
- Testing in “Airplane” mode in Android Emulator
- Reading data from Excel in Haskell
- How can I make integration tests with google cloud
- I want to test a private method - is there somethi
- Elasticsearch Spring boot integration test
- Mark Gradle source folder as test source in Intell
Coding is by far better. With record-play systems if any aspect of the page changes you have to go rerecord the entire test suite. With coding and proper design you can then go change the functions that interact with that one area and all the tests will start to work.
I would say both -- record as much as possible, then tweak the recorded code to test as you need. That assumes, of course, that your recorder emits code you can edit.
I've worked a lot with the Selenium browser automation software packages, and I find that recording re-inforces the existing application design, while coding drives the design in a flexible and maintainable direction.
Specifically, the practice I've found works best is to write the script a high level, pretending that you have no idea what the existing HTML markup says. Try very hard to keep the script readable.
If the script doesn't run, don't change the script -- change the HTML. Add IDs or classes or titles to elements where the script "tells you" it wants them. It takes a little longer, but it ensures that your script is maintainable and obvious, and it makes further scripts much easier.
It also depends on the complexity of the web app you wanna test.
Saying it in a different way and thinking working in an office, depends as well on how close with the DEVELOPERS you are working.
Spending time looking for your app's functions and nomeclatures can sure be avoided when you known your DEVELOPER teams has your back.
What is your case?
PS: Coding is better ;)
So far QTP is the best. But keep in mind - it's a powerful platform first. If you don't want to sink in maintenance of record/playback scripts you will need to develop your custom framework (go for keyword-driven) or buy HP BPT.
There is a range of low budget and open source tools as well.