You definitely want to try to share your work with others. This applies to response maps, but also to many other things in iTest – such as session profiles, testbeds, reusable procedure libraries (stored in iTest test case files), form maps, etc.
The recommended way of sharing these kinds of files is via version control. iTest supports a variety of standard version control servers such as Subversion, CVS, etc. (iTest is built on top of Eclipse and can therefore take advantage of any version control system supported by Eclipse itself.)
In order to share your work, you need to make sure those files are in an appropriate iTest project, and you can put that project under version control for others to share. I won’t explain here how to use version control, but you can look this up in the iTest online documentation.
A project in iTest (represented by a top-level folder in the iTest Explorer view) may be a response map library. (Typically response map library projects are created via a wizard or using the File > New > Response Map Library.) This means that it is a container for response map files – typically for one type of device (or perhaps for a family of similar devices). If you have a family of devices, and some of these devices have response formats that others don’t, you can organize these response map libraries in a hierarchy if you want. But for now, let’s just assume that you have one response map library for each type of device involved in your testbed. Once you put that project under version control, you can share your work by creating new response maps in that project and when you are satisfied with your changes, you can perform a “check in” to upload your changes into the version control server.
Likewise, if you want to pick up any new or modified response maps that others have created, you can “update” your project from version control and you’ll get them into your own workspace.