KaneAI - World’s First E2E Software Testing Agent.Book a Demo Join TestMu Conference

How to use testFaultDetailResource method of com.consol.citrus.dsl.runner.AssertSoapFaultTestRunnerTest class

Best Citrus code snippet using com.consol.citrus.dsl.runner.AssertSoapFaultTestRunnerTest.testFaultDetailResource

Source: AssertSoapFaultTestRunnerTest.java

...224        Assert.assertEquals(container.getFaultDetails().get(1), "<MessageDetail><message>Something went wrong</message></MessageDetail>");225    }226    227    @Test228    public void testFaultDetailResource() throws IOException {229        reset(resource, applicationContextMock, soapMessage, soapFaultValidator, soapBody, soapFault, soapFaultDetail, soapFaultDetailElement);230        when(resource.getInputStream()).thenReturn(new ByteArrayInputStream("<ErrorDetail><message>Something went wrong</message></ErrorDetail>".getBytes()));231        when(soapMessage.getSoapBody()).thenReturn(soapBody);232        when(soapMessage.getFaultReason()).thenReturn(INTERNAL_SERVER_ERROR);233        when(soapBody.getFault()).thenReturn(soapFault);234        when(soapFault.getFaultActorOrRole()).thenReturn(SoapFaultDefinition.SERVER.getLocalPart());235        when(soapFault.getFaultCode()).thenReturn(SoapFaultDefinition.SERVER);236        when(soapFault.getFaultStringOrReason()).thenReturn(INTERNAL_SERVER_ERROR);237        when(soapFault.getFaultDetail()).thenReturn(soapFaultDetail);238        when(soapFaultDetail.getDetailEntries()).thenReturn(Collections.singleton(soapFaultDetailElement).iterator());239        when(soapFaultDetailElement.getSource()).thenReturn(new StringSource("<ErrorDetail><message>Something went wrong</message></ErrorDetail>"));240        when(applicationContextMock.getBean(TestContext.class)).thenReturn(applicationContext.getBean(TestContext.class));241        when(applicationContextMock.containsBean(SOAP_FAULT_VALIDATOR)).thenReturn(false);242        when(applicationContextMock.getBean(TestActionListeners.class)).thenReturn(new TestActionListeners());243        when(applicationContextMock.getBeansOfType(SequenceBeforeTest.class)).thenReturn(new HashMap<String, SequenceBeforeTest>());244        when(applicationContextMock.getBeansOfType(SequenceAfterTest.class)).thenReturn(new HashMap<String, SequenceAfterTest>());245        MockTestRunner builder = new MockTestRunner(getClass().getSimpleName(), applicationContextMock, context) {246            @Override247            public void execute() {248                assertSoapFault().faultCode(SoapFaultDefinition.SERVER.getLocalPart())249                                .faultString(INTERNAL_SERVER_ERROR)250                                .faultDetailResource(resource)251                        .when(new AbstractTestAction() {252                            @Override253                            public void doExecute(TestContext context) {254                                throw new SoapFaultClientException(soapMessage);255                            }256                        });257            }258        };259        TestCase test = builder.getTestCase();260        Assert.assertEquals(test.getActionCount(), 1);261        Assert.assertEquals(test.getActions().get(0).getClass(), AssertSoapFault.class);262        Assert.assertEquals(test.getActions().get(0).getName(), "soap-fault");263        264        AssertSoapFault container = (AssertSoapFault)(test.getTestAction(0));265        266        Assert.assertEquals(container.getActionCount(), 1);267        Assert.assertTrue(container.getAction().getClass().isAnonymousClass());268        Assert.assertEquals(container.getFaultCode(), SoapFaultDefinition.SERVER.getLocalPart());269        Assert.assertEquals(container.getFaultString(), INTERNAL_SERVER_ERROR);270        Assert.assertEquals(container.getFaultDetails().size(), 1L);271        Assert.assertEquals(container.getFaultDetails().get(0), "<ErrorDetail><message>Something went wrong</message></ErrorDetail>");272    }273    @Test274    public void testFaultDetailResourcePath() {275        reset(applicationContextMock, soapMessage, soapFaultValidator, soapBody, soapFault, soapFaultDetail, soapFaultDetailElement);276        when(soapMessage.getSoapBody()).thenReturn(soapBody);277        when(soapMessage.getFaultReason()).thenReturn(INTERNAL_SERVER_ERROR);278        when(soapBody.getFault()).thenReturn(soapFault);279        when(soapFault.getFaultActorOrRole()).thenReturn(SoapFaultDefinition.SERVER.getLocalPart());280        when(soapFault.getFaultCode()).thenReturn(SoapFaultDefinition.SERVER);281        when(soapFault.getFaultStringOrReason()).thenReturn(INTERNAL_SERVER_ERROR);282        when(soapFault.getFaultDetail()).thenReturn(soapFaultDetail);283        when(soapFaultDetail.getDetailEntries()).thenReturn(Collections.singleton(soapFaultDetailElement).iterator());284        when(soapFaultDetailElement.getSource()).thenReturn(new StringSource("<ErrorDetail><message>Something went wrong</message></ErrorDetail>"));285        when(applicationContextMock.getBean(TestContext.class)).thenReturn(applicationContext.getBean(TestContext.class));286        when(applicationContextMock.containsBean(SOAP_FAULT_VALIDATOR)).thenReturn(false);287        when(applicationContextMock.getBean(TestActionListeners.class)).thenReturn(new TestActionListeners());288        when(applicationContextMock.getBeansOfType(SequenceBeforeTest.class)).thenReturn(new HashMap<String, SequenceBeforeTest>());...

Blogs

Check out the latest blogs from LambdaTest on this topic:

A Step-By-Step Guide To Cypress API Testing

API (Application Programming Interface) is a set of definitions and protocols for building and integrating applications. It’s occasionally referred to as a contract between an information provider and an information user establishing the content required from the consumer and the content needed by the producer.

How To Find Hidden Elements In Selenium WebDriver With Java

Have you ever struggled with handling hidden elements while automating a web or mobile application? I was recently automating an eCommerce application. I struggled with handling hidden elements on the web page.

Test strategy and how to communicate it

I routinely come across test strategy documents when working with customers. They are lengthy—100 pages or more—and packed with monotonous text that is routinely reused from one project to another. Yawn once more— the test halt and resume circumstances, the defect management procedure, entrance and exit criteria, unnecessary generic risks, and in fact, one often-used model replicates the requirements of textbook testing, from stress to systems integration.

Unveiling Samsung Galaxy Z Fold4 For Mobile App Testing

Hey LambdaTesters! We’ve got something special for you this week. ????

Two-phase Model-based Testing

Most test automation tools just do test execution automation. Without test design involved in the whole test automation process, the test cases remain ad hoc and detect only simple bugs. This solution is just automation without real testing. In addition, test execution automation is very inefficient.

Automation Testing Tutorials

Learn to execute automation testing from scratch with LambdaTest Learning Hub. Right from setting up the prerequisites to run your first automation test, to following best practices and diving deeper into advanced test scenarios. LambdaTest Learning Hubs compile a list of step-by-step guides to help you be proficient with different test automation frameworks i.e. Selenium, Cypress, TestNG etc.