This same method can be used to extract data that is used to set a variable. This is the usage model demonstrated in the Storing Results to Be Used in Subsequent Tests tutorial. You simply go to the tool where you want to insert extracted data, then use a wizard to specify what data (e.g., from what tool) you want to extract. This provides a quick, intuitive, and largely automated way to extract data from one tool and use it another. Users typically configure a JSON Data Bank in SOAtest by accessing the "Use Data Source Wizard" while parameterizing a value in a tool such as the REST Client or Messaging Client tool. You can configure any of the tests in a test suite to use JSON response parameters as JSON request parameters.
Test 2 of that test suite can be configured to use the session ID from Test 1 to perform transactions. Test 1 of that test suite can log on to the service using a User ID, then the JSON response would return a session ID back to Test 1. It can extract any information from the JSON and make that information available for later use.įor example, you can configure a test suite that tests a bank’s service transactions. The JSON Data Bank tool can be chained to any other tool that outputs JSON. This tool enables you to extract certain JSON values (e.g., from a request or response message) so that they can be used in another place. This topic focuses on the current JSON Data Bank implementation.For details on the deprecated JSON Data Bank, see JSON Data Bank Deprecated. The previous implementations are deprecated: any existing tools will continue to work, but all new JSON Data Banks you add will use the new implementation. The JSON Data Bank tool was re-implemented in version 9.7.
0 kommentar(er)
