All geek questions in one place

How to succeed in testing the web interface?

We are creating a Selenium test campaign in a large web application. The first thing we did was create a structure that initializes the SQL data in the database before the test, starts the test, archive results and then cleans the data.

We integrate this into the Maven 2 process, every day we run TeamCity in a dedicated database.

We installed several Selenium tests, but not as planned.

The reasons why tests are sometimes interrupted for reasons other than regressions (data can be modified, stored procedure may have been recompiled, and so on).

I would like to know if there is great success in testing the user interface, and if so, then the reasons. Commons bugs may also interest me.

+3
source share
3 answers

. - - HTML, , . , HTML- (Selenium xpath), / , . , , ( Selenium) -.

+1

, . . , . , , unit test ( , , ).

, . , , , , . , , , , "" .

+1

http-unit, , - .

http://httpunit.sourceforge.net/ maven2.

Written in Java, HttpUnit emulates the relevant parts of browser behavior, including form submission, JavaScript, basic HTTP authentication, cookies and automatic page redirection, and allows Java validation code to validate returned pages as text, XML DOM, or containers of forms, tables and links.

0
source

Source: https://habr.com/ru/post/1697652/

More articles:


All Articles