SOA testing

How SOA testing differs from traditional application testing

+3
source share
6 answers

Think that you must remember that in an environment where there are many dependencies, you must have all the dependencies mapped and all paths should be tested.

Using services, they should be used with a large number of clients, so each client should follow the test cases.

Using services, you also need to pay attention to network problems. Do traditional tests, putting a lot of traffic on the network and turn it off to see how it works.

In addition, the provision of services does not require a different approach. Just control all inputs and outputs.

0

" " - ( WSDL), :

  • , .

  • , , .

  • , , ; , - , - .

Edit:

  • , , , . , - Internet Explorer, , , . SOA, , .
+2

SOA , WSDL, , () .

, SOA , , , , -, .

, , , , , , :

  • : , , , , , .
  • : ( xml) , , , . . , , , .

: SOAP UI JMeter, .

+1

(?) :

Mock , .

: , , .

0

SOA .

, , , , , ( , ), , ( -), ..

, , , , , , .

0
source

Soa testing simply ensures that all independent services behave as expected, all the while adhering to the input and output contract established by these services. I found an interesting tool for testing SOA, and it is FREE SOArite .

0
source

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


All Articles