File virtual service architecture

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.

Files architecture diagram Virtual service replaying files from a request directory to a response directory

Add/Edit mappings


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.


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: Root directories dropdown screenshot

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

To define a new root directories that will be available in the dropdown in the record and replay panels:
  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
If you would like to change the location of the root-directories.json file, change the value of property
to for example
This can be useful if you would like to version control it with your application source code.

Proof of concept with on-premises installation at a large enterprise

See proof of concept in the user guide.

Custom extensions

Have a look at available extensions