File Transfer

A tester or developer uses a web browser to access the console. The console manages the virtual service. The system under test (application under test) connects directly to the virtual service on different ports.

Here is an example of how that could look like for a scenario where the virtual service is replaying files.

Virtual service replaying files from a request directory to a response directory

Usage

First, go to Files in the top navigation bar and then click Add/Edit.

Fill in the Request/Response fields and click Save to configure a mapping.

After saving the mapping, it will appear in the list of mappings.

Clicking the edit button will allow you to edit an existing mapping.

Priority

When Traffic Parrot notices a request files, it will try to simulate the system it is replacing by creating a response file in the specified directory. To decide what is the name and content of the response file, it will go through all the request to response mappings it has available to find the response file definition. For more details how request matching works, see Request matching.

There are several matchers available to match request files, depending on the attribute.

{
  "name": "{{ anyValue }}",
  "lastName": "{{ anyValue }}",
  "age": "{{ anyNumber }}",
  "children": "{{ anyElements }}"
}

{
  "name": "Bob",
  "lastName": "Smith",
  "age": 37,
  "children": [{"name": "sam"}, {"name": "mary"}]
}

$[?(@.xyz.size() == 2)]

{"xyz":[{"a":true}, {"b":false}]}

{"xyz":["a":true, "b":false, "c":true]}

<example>
  <name>{{ anyValue }}</name>
  <age>{{ anyNumber }}</age>
  <children><tp:AnyElements/></children>
</example>

<example>
  <name>Sam</name>
  <age>29</age>
  <children><child name="bob"/></children>
</example>

/xyz[count(abc) = 2]

<xyz><abc/><abc/></xyz>

<xyz><abc/></xyz>

Define root directories

To record from or replay to file systems you will need to tell Traffic Parrot which root directories to use.

Those root directories are displayed in the dropdown menus on the record and replay panels, for example:

All directories that are configured when e.g. adding a mapping are relative to the selected root directory.

1. Open root-directories.json file located in the main Traffic Parrot directory, using your favourite text editor
2. Add the new root directories (make sure the id field has a unique value!). An example content of the file, with 2 root directories defined:

   [
     {
       "id": "1",
       "name": "C Drive",
       "rootDirectory": "C:\\some\\root\\directory"
     },
     {
       "id": "2",
       "name": "Network Drive",
       "rootDirectory": "\\network\\share"
     }
   ]

3. Note that the \ character must be escaped as \\
4. Save the file
5. Refresh the page in Traffic Parrot to reload the dropdown list.

In the current Traffic Parrot version you edit root directories directly in the root-directories.json file. In near future you will be able to do it via the Web UI as well.

Change the location of root-directories.json

trafficparrot.virtualservice.rootDirectoriesUrl=classpath:root-directories.json

trafficparrot.virtualservice.rootDirectoriesUrl=file:/home/john/git/project/root-directories.json