What exactly do you automate in automating user interface testing?

All the documents that I have read so far on various test platforms (Selenium, Tellurium, Canoo, etc.) encourage (or at least concentrate) on functional testing of the application through the user interface. I saw very less on the bottom, which, in my opinion, is the most important.

  • localization testing
  • usability testing
  • cross browser compatibility testing
  • testing multiple versions of the same browser
  • xss / sql injection
  • check
  • Is the user interface / presentation layer a call to the correct service level API (the service level is fully tested through component-based testing).

So here are my questions

1) What exactly do you automate in the automation of user interface testing?

2) What user interface testing environment can fit all of the above elements?

+5
source share
2 answers

I have used Selenium in the past, and it works great for all 1-7, with the possible exception of localization, since I did not need to check this. Like 2, the applications I tested were basically just “writing something in the text box and see if it works,” so it was pretty easy. And, for 4, I had several virtual machines with only certain browsers installed. It was a hack, but it worked, sort of.

+1

, . . , .

Framework, . , , eggPlant (TestPlant). . jmeter REST . -. selenium, .

- - Selenium Grid junit .

0

All Articles