Idea ID 1792284
this is my idea (and needs ^_^).
In a typical NR activity, we create test suites to store targeted gherkin tests that we're planning to run BUT, often, we don't want to run the whole GT scenarious (because of budget-constraint or business-related preconditions not met).
We can already do it (running partially a GT and assigning manually a GT status), but what happens when we report/analyze the quality? We can't drill down on how many scenario of a single GT has been run, so we don't have a clear picture of which scenario has been run and which not and therefore we don't have a real quality/risk analysis for the current activity.
So, what I'm suggesting is to add a "real" scenario entity in Octane (or, at least, an API for retrieving scenario-level informations), in order to manage scenarios and their relations.
Thanks for everybody reading (and voting! ^_^)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.