[feature request] lava-test-shell parameters not displayed in the result table

When running the same test definition multiple time in a job, there is no way to distinguish between subsequent runs if there are different parameters used. Example job definition:

...
        {
            "command": "lava_test_shell",
            "parameters": {
                "testdef_repos": [
                    {
                        "git-repo": "git://git.linaro.org/people/milosz.wasilewski/test-definitions.git",
                        "parameters": {
                            "TST_CMDFILES": "syscalls"
                        },
                        "testdef": "openembedded/ltp.yaml"
                    }
                ],
                "timeout": 7200
            }
        },
        {
            "command": "lava_test_shell",
            "parameters": {
                "testdef_repos": [
                    {
                        "git-repo": "git://git.linaro.org/people/milosz.wasilewski/test-definitions.git",
                        "parameters": {
                            "TST_CMDFILES": "math"
                        },
                        "testdef": "openembedded/ltp.yaml"
                    }
                ],
                "timeout": 7200
            }
        },
...

The above definition will produce the following result table (in the bundle view):

Device Test Run Test Passes Fails Uploaded On Analyzed On Bug Links
wg-04 lava results lava 21 0 2014-05-20 21:12:39 2014-05-20 16:07:15
wg-04 ltp-oe results ltp-oe 2 0 2014-05-20 21:12:39 2014-05-20 17:07:05
wg-04 ltp-oe results ltp-oe 19 0 2014-05-20 21:12:39 2014-05-20 17:52:03
...

Since the list of parameters might be long there is no easy way of displaying the information in the table. However the following solutions might be considered:

1. display fixed length preview next to test ID, example:
ltp-oe ("TST_CMDFILES": "math")
If there are more parameters:
ltp-oe ("TST_CMDFILES": "math", "PARAM2": "Value 2")
or
ltp-oe ("TST_CMDFILES": "math", "PARAM2": "Val...)
in case the maximum length was reached

2. display a tooltip 'on-mouse-over' listing all parameters

The above solutions may be used together.

On top of that I would like to have the list of parameters and their used values in the CSV file associated with the bundle. The parameters and their values are available from the result bundle (test_runs->software_context->sources->test_params).