Rows in table driven scenario are wrongly linked

[mahendrakariya]

Expected behavior

In a table driven scenario, when a user clicks on a row, reports should show details for that particular row.

Actual behavior

In a table driven scenario, when a user clicks on a row, reports are show details for some other row.

Steps to reproduce

1. Create a new table driven spec.
2. Run a few rows of the table excluding the first row. So, something like gauge --table-rows="3-7" specs

[mahendrakariya]

Dependent on getgauge/gauge#363

[apoorvam]

The dependent issue getgauge/gauge#363 is fixed and this is implemented in commit.

Fix should be available in nightly >= 26.10.2016

[sswaroopgupta]

when the entire spec is skipped, all the table rows are still green. Another thing to be taken care of is when I click the skipped row, I should be able to see the details of the spec.

Specification Heading
=====================
tags: top

     |table|d1|d2|3d|d|
     |-----|--|--|--|-|
     |d    |d |  |d |d|
     |d    |d |  |d |d|
     |d    |d |  |d |d|
     |d    |d |  |d |d|

* volume
c
-
tags: scenario3 ppp a b c d e f g h i j k l m n o p q r s t u v w x y z

* Criaçãosdf

c1
--
tags: scenario3 ppp a b c d e f g h i j k l m n o p q r s t u v w x y z

* pass
mhvbmh
___
* pass

[apoorvam]

Dev notes:

when the entire spec is skipped, all the table rows are still green.

In order to fix above issue, changes has to be done in Gauge-core.

When a table-driven spec is skipped for steps being unimplemented, the field IsTableDriven in ProtoSpec is not set to true. It retains the default value of bool, false.

Also, the scenario results for all the table rows is not updated. The method SkipSpec() here uses specResult.AddScenarioResults() method, whereas in case of table driven spec it should use specResult.AddTableDrivenScenarioResult() to update all fields.

[apoorvam]

when the entire spec is skipped, all the table rows are still green.

This particular case is already tracked in issue #101. So this can be closed?