You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each scenario is technically a single test, so the build summary statistics should summarise all scenarios rather than all features.
Many feature files contain a mix of manual and automated scenarios, which means the reported proportion of "manual" tests is much higher than reality. Similarly, one failing scenario causes the proportion of "failing" tests to appear much higher than reality.
Discussion in HipChat room:
Current behaviour (feature-based) is useful for regression testing; this could be retained as an option.
Reporting / Printing still makes sense on a per feature basis.
The text was updated successfully, but these errors were encountered:
iamam34
changed the title
Dashboard stats summarise features rather than scenarios
Dashboard stats could summarise scenario rather than features
Dec 10, 2015
iamam34
changed the title
Dashboard stats could summarise scenario rather than features
Dashboard stats could summarise scenarios rather than features
Dec 10, 2015
Each scenario is technically a single test, so the build summary statistics should summarise all scenarios rather than all features.
Many feature files contain a mix of manual and automated scenarios, which means the reported proportion of "manual" tests is much higher than reality. Similarly, one failing scenario causes the proportion of "failing" tests to appear much higher than reality.
Discussion in HipChat room:
Current behaviour (feature-based) is useful for regression testing; this could be retained as an option.
Reporting / Printing still makes sense on a per feature basis.
The text was updated successfully, but these errors were encountered: