Better Software - March 2008 - (Page 28)

sure that the target Web service behaves as expected. For the Add operation, test cases may include positive and negative test cases. For positive test cases, sending simple integer input values to the Web service ensures that the operation can indeed add the two input values, a and b. Negative test cases that send very large values, incorrect data types, and special characters also can be used to ensure that the Web service handles them as expected, returning error codes or throwing exceptions. Functional Testing Caveats As testers become comfortable with SOA functional testing and move beyond the simple Web service that we have created and tested here, the following items should be noted: • Loading WSDLs: The starting point for testing a Web service is importing a WSDL from a Web services application. With WSDLs being generated by a variety of systems such as application servers (WebLogics, WebSphere, Figure 6: Setting test cases for Add(int a, int b) operation JBoss, Tomcat, NetWeaver), RDBMS (Oracle 10g, IBM DB2, MS SQL Server), and SaaS providers (Salesforce.com, NetSuite, SugarCRM), the first hurdle faced by testers is importing and parsing WSDLs so that they can navigate to the desired operation for building test suites. • Broad Standards Support: With a WSDL imported and an operation selected, a SOA tester may have to perform a number of tasks within the SOAP request before sending it to the Web service. Beyond basic WSDL and SOAP standards, Web services standards that are widely used include WS-Security 1.1 for Encryption, Signatures, and Identity Profiles (SAML, User Name, X.509, Kerberos), WS-Addressing, WS-Reliable Messaging, and WS-Policy. Figure 7: Setting test suites for Add(int a, int b) operation • Test Management: Once the desired operations and associated The login operation responds with a session token. This tasks are defined, the tester must session token then must be passed for every pAdd(int a, focus on test management including chained WSDL opint b) test case. Setting up a chained operation sequence erations. For example, we may have a protected Web test case such as login(user, password) → pAdd(int a, int service operation pAdd(int a, int b) that can only be inb) is typical for testing real-world SOA deployments. voked after a login (user, password) operation is called. 28 BETTER SOFTWARE MARCH 2008 www.StickyMinds.com http://www.StickyMinds.com

Table of Contents Feed for the Digital Edition of Better Software - March 2008

Better Software - March 2008 Contents Mark Your Calendar Contributors eLightenment Technically Speaking Code Craft Test Connection Management Chronicles Cover Story: Breaking Ground On SOA Software Development Worst Practices Mind the Gap Product Announcements 10 Things You Might Not Know About... The Last Word Ad Index

Better Software - March 2008

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.