Block mapping is a big topic. You can start with reading our help. There is also response mapping tutorials available from Fanfare support. If you can post an example response which you are having hard time mapping using block mapping, we can help you here on the forum.
If you take the following simple example:
Interface 1:
packets sent = 100
packets received = 200
Interface 2:
packets sent = 173
packets received = 300
You can visualize that the response is composed of two blocks which are very similar with only certain numeric fields changing. What you will do in this case is:
1. Create a block in the container tree in the block mapping page.
2. In the text box on the right for the block, you will paste in the contents of a single block:
Interface 1:
packets sent = 100
packets received = 200
3. You will set various block properties on the block like whether it repeats, or is optional.
4. You will notice that iTest has already parsed out various tokens in the block and marked the numeric tokens as variables (because these can change).
5. You can name these numeric variable tokens to the names you would want.
6. You can open the "Step issues" view to see if your response has mapped successfully or has some errors.
7. You can tweak the block map properties to get rid of the errors.
8. Finally, on the queries page, you can add some XPATH queries to extract data from your map. In this case you probably want to create two XPATH queries: packets_sent_by_interfaceid(interfaceid) and packets_received_by_interfaceid(interfaceid).
9. Once you have created the queries, your response map is ready to be used in the testcase. You can now use these queries from the response map in analysis rules or for iterations.
