This introduction serves as a high-level overview of the different test approaches and tools, including Java Explorer, Java Framework, .NET Explorer, and .NET Framework, that are offered by Silk Performer Service Oriented Architecture (SOA) Edition.

Silk Performer SOA Edition Licensing

Each Silk Performer installation offers the functionality required to test .NET and Java components. Access to Java and .NET component testing functionality is however only enabled through Silk Performer licensing options. A Silk Performer SOA Edition license is required to enable access to component testing functionality. Users may or may not additionally have a full Silk Performer license.

What You Can Test With Silk Performer SOA Edition

With Silk Performer SOA Edition you can thoroughly test various remote component models, including:

  • Web Services
  • .NET Remoting Objects
  • Enterprise JavaBeans (EJB)
  • Java RMI Objects
  • General GUI-less Java and .NET components

Unlike standard unit testing tools, which can only evaluate the functionality of a remote component when a single user accesses it, Silk Performer SOA Edition can test components under concurrent access by up to five virtual users, thereby emulating realistic server conditions. With a full Silk Performer license, the number of virtual users can be scaled even higher. In addition to testing the functionality of remote components, Silk Performer SOA Edition also verifies the performance and interoperability of components.

Silk Performer SOA Edition assists you in automating your remote components by:

  • Facilitating the development of test drivers for your remote components
  • Supporting the automated execution of test drivers under various conditions, including functional test scenarios and concurrency test scenarios
  • Delivering quality and performance measures for tested components

Silk Performer offers the following approaches to creating test clients for remote components:

  • Visually, without programming, through Java Explorer and .NET Explorer
  • Using an IDE (Microsoft Visual Studio)
  • Writing Java code
  • Recording an existing client
  • Importing JUnit or NUnit testing frameworks
  • Importing Java classes
  • Importing .NET classes