ESB Testing
Download as PPTX, PDF1 like335 views
The document provides an overview of the integration between the Homeserve USA HS Business application and the Ensura ERP system using Talend ESB. Talend ESB acts as an intermediate message transfer service, facilitating requests from the HS Business application to the Ensura application and responses back. A number of services are described for the ESB including contract, customer, partner, payment, sale and more. SoapUI NG and LoadUI NG will be used for functional testing, data driven testing, and load/performance testing of the services.
ESB Testing
- 1. Project Overview Homeserve USA is holding an ERP system called ensura where we will hit all our requests from HS Business application to ensura through talend ESB and get the response from ensura application through talend ESB acts as an Intermediate message transfer for ensura and HS Business application. We can call the • Provider as Ensura • Consumer as Web channel (HS Business Application) For more details please refer the business requirement spec HS Business Application Ensura (ERP) Application Talend ESB
- 2. Overview on ESB Phase I Services and their Operations Contract Service getContractDetails getRenewalEligibilityDetails getRenewalDetails processRenewal updatePaymentType Customer Service addPaymentDetails getPaymentDetails validateAddress getCustomerDetails updateAddressDetails PartnerService getPartnerDetails validatePartnerDetails
- 3. Payment Service validatePaymentDetails Sale Service getProspectDetailsRequest validateOffer validateSale processSale Overview on ESB Phase I Services and their Operations
- 4. Overview on ESB Phase II Services and their Operations Contract Service getContractDetails (Change request added new output parameter’s) Customer Service getCustomerDetails (Change request added new output parameter’s) Sale Service getProspectDetailsRequest (Change request added new output parameter) processSale (Change request added new output parameter)
- 5. Overview on ESB Phase III Services and their Operations Customer Service processEmailConsent (New operation has been Added) Sale Service getProspectDetailsRequest (Change request added new output parameter) processSale (Change request added new Input parameter)
- 6. Overview on ESB Phase IV Services and their Operations Customer Service getCustomerDetails (Change request added two new output parameter’s) ProcessCustomerPaperlessChange (New operation has been Added)
- 7. Overview on ESB Phase V Services and their Operations Customer Service ProcessPaymentDetailsChange (New operation has been Added) getPaymentDetails (Change request added new output parameter) validateAddress (Change request added new Parameters for both input and output) getCustomerDetails (Change request added new output parameter) updateAddressDetails (Change request added new Input parameter)
- 8. Overview on ESB Phase VI Services and their Operations Sale Service ProcessVendorSale (New operation has been Added)
- 9. Role of QA in HomeServe ESB Testing Go through the requirement documents like (Wiki Links, BRD) and understand the requirements. Prepare the Integration document according to the change or new operation added into the respective service. once we are done with Integration document wait for approval and then start preparing the test artifacts accordingly. Once we got an approval for Integration document then we will start writing the test scenarios and again wait for approval. once it is approved then we will go ahead with test cases accordingly. Once we get the approval for test artifacts then we will move forward for Functional Testing. Once we are done with functional testing we will update the results in test document and start working on data driven testing in SOAPUI NG export the results and wait for load test results. After performing load test in LOADUI NG will start looking into test metrics for the TPS,Min,Max,BPS and export the test results in PDF format and send it for approval.
- 10. SoapUI NG is a web service testing application for service oriented architecture (SOA) and representational state transfer (REST), simple object access protocol (SOAP). Its functionality covers web service inspection, invoking, development, simulation and mocking, functional testing, load and compliance testing. • Generate your test from your API's service description then use the Test Coverage feature to dynamically analyze your functional test coverage • Use external data sources to react quickly when you need to simulate different user behavior without recreating your test case • Speed your API testing with point-and-click property transfer and assertions LoadUI NG Pro is for professionals and businesses that really need to be sure about the performance and scalability of your APIs, there's LoadUI NG Pro which includes distributed load testing, server monitoring, visualizations, and advanced scenario simulation. Overview of SOAPUI NG & LOADUI NG
- 11. Testing Cycles Involved in Homeserve ESB Dev Environment Test Environment Regression Testing Dev & Test Environment: • Once we get the approval for test artifacts we will get the endpoint from development team. • Once we receive endpoint from development team we will try to start Invoking the endpoint in soapUI NG and create the new project. • Once we are done with creating the new project then try to create the SAML Token (Security Assertion Markup Language) and Apply the same for the above created project in local and global areas for security enabling to the service for proper response which stands for only 8 hrs from the token generation. • Then start doing functional testing by passing all the test data manually according to the test scenario’s and test cases which includes populating the error codes. • Once we are done with functional testing then we will move to data driven where we will cook some sample data and try to load the same into SOAPUI tool and run the data driven.
- 12. • Once we are done with data driven then we will export the results and check the transaction logs for few requests and cross verify. • After doing data driven we will do the performance testing like load test by passing some virtual users and give the wait time which will enable the time between each request. • Once we are done with running load test we will check the TPS (Transaction per second) is populating well will send the data driven and load test reports for Approval. NOTE: For test environment in additional we will provide the documentation of each and every request in functional testing according to the test scenarios. Regression Testing: Once we do the testing for Ready to Test Issues then we will do the Regression Testing of all the Scenario’s once again for any intermediate changes in the service or operation which is not at their behavior. Testing Cycles Involved in Homeserve ESB
- 13. Sample Request and Response in Functional Testing
- 14. Sample Execution Metrics for Data driven
- 15. Sample Execution Metrics for Load test
- 16. Thank You!