Concept arguments not showing up in step text.

[ConfusedSky]

When using a concept the parameters that are passed in don't show up anywhere in the json report. For example

## Login with concept
* Log into github as "TacoTestAccount" using password "testAcountPassword".

shows up in the report as is with no substitution

"itemType": "concept",
    "conceptStep": {
        "itemType": "step",
        "stepText": "Log into github as \u003cusername\u003e using password \u003cpassword\u003e.",
        "table": null,
        "beforeStepHookFailure": null,
        "afterStepHookFailure": null,
        "result": {
            "status": "pass",
            "stackTrace": "",
	    "screenshot": "",
	    "errorMessage": "",
	    "executionTime": 9317,
	    "skippedReason": "",
	    "messages": [],
	    "errorType": "assertion"
}

Expected Behaviour

Have some way to determine what was passed into the concept. Either through the step text or as another json property.

Version

Gauge version: 1.0.3
Commit Hash: ff6c0c3

Plugins
-------
flash (0.0.1)
html-report (4.0.6)
js (2.3.2)
json-report (0.2.2)
python (0.3.4)
screenshot (0.0.1)
xml-report (0.2.1)

[apoorvam]

@ConfusedSky I have now added a new field Parameters in step to include all the various types of parameters with their values, including static parameters, dynamic, table and special params.

Example:

{
	"itemType": "step",
	"stepText": "The word \u003cword\u003e has \"3\" vowels.",
	"parameters": [{
			"parameterType": "dynamic",
			"name": "word",
			"value": "gauge",
			"table": null
		},
		{
			"parameterType": "static",
			"name": "",
			"value": "3",
			"table": null
		}
	],
	"beforeStepHookFailure": null,
	"afterStepHookFailure": null,
	"result": {
		"status": "pass",
		"stackTrace": "",
		"screenshot": "",
		"errorMessage": "",
		"executionTime": 0,
		"skippedReason": "",
		"messages": [],
		"errorType": "assertion"
	}
}

You can checkout full schema here:
https://apoorvam.github.io/json-report/
The field table which was present earlier inside a step is removed, since it will be included in parameters.

Will make a release with these changes soon. Let me know what you think.

[ConfusedSky]

Thanks! This is exactly what I was looking for. I appreciate the hard work!

[apoorvam]

Great! @ConfusedSky Can you please let me know your use case of using json-report with Gauge? It helps me understand the applications of it more.

[ConfusedSky]

I use it to get a historical baseline of test performance. I have it categorized by spec, scenario, and step. So I can see which steps themselves take the most time.

Parameterized steps would often have the highest variance in duration but there was no way of determining what the problem parameters were from the json-report alone, until now.

[apoorvam]

@ConfusedSky Thanks for that. json-report (0.3.0) is now released with this enhancement. Give it a try! Closing this issue now :)

[ConfusedSky]

Following up, everything is looking good! I appreciate the effort!