Testing a .NET Web Service

Before proceeding, start the message server.

Note: This scenario is stored within your Silk Performer installation. You can access it at <public user documents>\Silk Performer 21.0\SampleApps\DOTNET\Message Sample\NetExplorer_TestingWebService.
  1. Launch Silk Performer and create a new project.
  2. Load the WSDL from the Web service: http://localhost/MessageWebService/MessageService.asmx?WSDL
  3. Invoke the login method using User1 and Pass1 as input values.

    You can also use random variables or global variables mapped to attributes (see .NET Explorer Help for details).

  4. Send a message with some text from User1.
  5. Logout the current user and login as User2 (username: User2; password: Pass2).
  6. Invoke GetMessageCount and store the result in a variable called mCount.
  7. Call GetMessage with the message count variable as input. You will receive the last message that was sent.
  8. Add the remaining logout method call.
  9. Execute an animated run. The failed verification can be ignored (or you can remove the default verification of the GetMessageCount call).
  10. Export a Silk Performer .NET project or a Visual Studio .NET project (exported projects can be found at <public user documents>\Silk Performer 21.0\SampleApps\DOTNET\Message Sample\NetExplorerExportedProject).
  11. Execute a Try Script run via Silk Performer or Visual Studio .NET.
  12. Explore the TrueLog. You will see a node for each Web service call.