For all testing automation experts :-)! I would like to hear your opinion on the following scenario:
There is a web application that I need to check. I have to run basic tests on the server and front tests on the client. I also need to run end-to-end tests, including both external and front-end.
The server provides web services (SOAP), and the external client uses the data from these services. There are also third-party clients consuming data from web services. Sometimes a test case requires me to do end-to-end tests, i.e. I make some changes to the GUI, and then use the web service on the internal server to see if the changes were successful or not.
I like FitNesse - in my opinion, separating WHAT and WHY from HOW is important for developing good tests. There is a Selenesse module that allows you to integrate Selenium tests with FitNesse wiki pages. This makes it easy to describe what and why I need to check something (wiki text) from how I want to test it (script tables and script tables), which is what I want.
The problem with FitNesse is that it is somewhat cumbersome to test SOAP web services. Either I need to develop a specially created Java tool for the SOAP client, or I have to write Java devices that extend the ServiceFixture class written for FIT. In any case, the development effort is much greater than if I implemented these tests in soapUI .
In my opinion, the drawback with soapUI is that there is no easy way to explain the WHAT and WHY test (at least not as intuitively).
, , , GUI FitNesse/Selenesse back-end- soapUI. soapUI FitNesse, FitNesse soapUI...
, ( ) keepablity ( ) . - / ? ?