-1

We are planning to have two separate automation tools to automate our current application, as tool-1 does not support some critical functions. Integration is difficult between these two tools. Will it be a good idea?

The application we are testing is based on electron, for which we are using spectron with jasmine. However, the application heavily uses drag and drop of controls - for which spectron does not have any support and so does webdriver.io.

We also tried to integrate selenium but we had no luck in integration due to Action class integration issue. We are thinking of using a different tool which supports drag and drop and running only those test cases on the other tool.

1

It depends

There is nothing wrong with using two different tools to automate an application if those tools solve a problem that you can't otherwise get around.

Some things you might like to consider:

  • How likely is it users will use the feature that needs your second tool?
  • How likely is it that there will be regression problems with the GUI interface and those features? (even if the application has not been released, if that part of the system has been problematic, it's likely that it will continue to be problematic).
  • How much extra work is the second tool likely to add for your team, and does the ROI of that work justify purchasing and using the second tool? (that is, if it will take you 50 hours to add the automation you need using tool 2, and then 5 hours per week to maintain it, but you could do the same tests manually in 2 hours per week, it's probably not worth automating)(the numbers are random)
  • How much of the functionality you're planning to automate with the new tool is covered by unit tests?

If after you've considered these factors (it's not a complete list, but it's a decent starting point) it looks as though the second tool will be worth your while, then it's a good idea to use it. If it looks as though you're going to spend more time modifying your tests and trying to figure out flaky tests, then it probably isn't a good idea.

Either way, you'll want to start with an evaluation version (if the tool is not free and open source) and see if it will work for you before you make the decision.

If you do decide to use it, make sure to build the tests into your CI pipeline so they are run regularly, if possible

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.