Skip to content

Platform Guides

Most web applications fall into the standard pattern: HTML forms, session cookies, OAuth tokens, the kind of thing ASM was built to handle. A few don't. REST APIs have no browser flow at all and are tested differently. SOAP-based web services use XML envelopes with their own correlation conventions. Salesforce has its own session-id and organization-id machinery that requires platform-specific rules. The pages in this section cover those cases.

If your application is a standard web app, you don't need this section. Use the Configuring chapter and the platform-detection rules ASM applies automatically.

In This Section

  • REST/API Testing: Test cases that consist entirely of REST API calls, with no browser-driven HTML pages. How to record them, how to vary inputs, how to handle authentication tokens.
  • Web Services (SOAP): SOAP-over-HTTP endpoints with XML request and response envelopes. WS-Security, signed envelopes, and correlation patterns specific to SOAP.
  • Salesforce: Salesforce-specific session and organization tokens, view-state handling, and the platform detection rules ASM uses for Force.com and Lightning apps.
  • Other Platforms: SAP, Oracle, SharePoint, and the long tail of enterprise platforms with their own state-management quirks.

These guides are reference material, not workflow steps. Read the one that matches your application. The rest don't apply.