Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. COThanks David. Well in our applcation we are using spring jdbc to connect to DB and also using Spring Webservices to connect to external webservices and not relying on Mule for the same. How do you reckon we should handle that situation? Also can you kindly answer why need to wrote separate mule-config xmls for tests? Should we not be able to test teh actual Production config xml as thats what we are testing. Creating separate files kind of defeats the purpose
      singulars
    2. COUse whatever technique is recommended by Spring to test the beans that use Spring JDBC and webservice, this has nothing to do with Mule. If you intend to run your tests against the production infrastructure then use a single file but you'll need to flag these messages as test ones otherwise you'll mess production data. And no it doesn't defeat any purpose: there's value in testing in isolation, for example to prove that the flows, the transformers they contain, etc... behave as expected.
      singulars
    3. COThanks David. When I said running tests against production infratructure I meant the same flow file that is deployed in production. However while running the tests I will be stubbing out external services and databases and also point to test versions of the same instead of Live sources. I have noticed in Mule docs that they kind of copy the flow xml file into a new test file and write tests on them. e.g in future if I change the actual flow xml file I also need to copy the same changes in another test file. One would expect to run tests and Live on the same piece of code i.e. flow config file
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload