HTTP(S) Recording using AMF Externalizable Types

Document created by Chris Sommerstad Employee on Jul 20, 2017
Version 1Show Document
  • View in full screen mode

CloudTest provides support for HTTP(S) recording of Action Message Format (AMF) externalizable types. Users can upload the necessary serialization code into CloudTest using a Custom Module, and then specify that module prior to initiating a recording.

Note: This feature requires that you create a custom module using your code. Refer to Custom Modules if you haven't added such a module as yet.

Users can setup AMF externalizable types via the Recording Editor (using Central > Recording) by checking the box provided.

Users can do the same using the Clip Editor's HTTP recording command by checking the box provided.

TIP: For more about HTTP(S) recording using CloudTest, refer to Creating an HTTPS Recording if you will be using the Recording Editor, or refer to HTTP Recording into the Clip Editor if you're recording will be performed there.

  1. Before starting an HTTP(S)recording session in the Clip Editor, click the Custom Modules tab and check "This recording uses AMF externalizable types" to list the Custom Modules.
  2. Check the box for themodule to use to decode the binary AMF content.

While recording, the module(s) will be used to produce the correct AMF XML representation. 
CloudTest will store the list of custom modules to use inside the target definition. Target settings can be manually configured via the Content Options section, Response Encoding section.

  1. Check AMF Custom Modules required and then click Choose custom modules to select the repository custom module to use.

Note: The conversion process only stores the modules in the target for messages that actually use AMF.

When playing a Composition, Maestro will provide this list of custom modules to the underlying Transport Layer. The Transport Layer will use the custom modules to convert HTTP requests and responses from XML to AMF and vice-versa.

Attachments

    Outcomes