First of all create a list of criteria for tool selection (Exemplary check list of QF-TEST)

On the one hand you surely have several "must have" criteria in mind like the supported technologies, platforms, INTEGRATION in the build process or stable recognition of graphical elements of your SOFTWARE. On the other hand there are "nice to have" criteria that you would give up in favor of another aspect. You then can test, evaluate and COMPARE the different tools regarding these criteria. Then you only have to choose one.

Another aspect is how you want to create the test: Do you want to code or record them via capture/replay; do you follow a keyword-driven or behavior-driven testing (BDT) approach.

Most importantly the test TEAM should accept the tool.

First of all create a list of criteria for tool selection (Exemplary check list of QF-Test)

On the one hand you surely have several "must have" criteria in mind like the supported technologies, platforms, integration in the build process or stable recognition of graphical elements of your software. On the other hand there are "nice to have" criteria that you would give up in favor of another aspect. You then can test, evaluate and compare the different tools regarding these criteria. Then you only have to choose one.

Another aspect is how you want to create the test: Do you want to code or record them via capture/replay; do you follow a keyword-driven or behavior-driven testing (BDT) approach.

Most importantly the test team should accept the tool.