Define behavior for nesting describe/steps

[nyarly]

Behavior is currently undefined. Easiest thing would be to fail completely if steps not at root or anything nested.

[vasilakisfil]

hi! How difficult would it be to enable nested steps? I think a nested step should execute all steps before that but not steps in the same indentation (same block ? ). That would help a lot in scenarios that differ slightly.

[nyarly]

There's a number of use cases, and it's not entirely clear how to handle them in a straightforward way.

Picture:

steps "outside" do
  it "1" {}
  steps "in a" do
    it "1a" {}
  end
  it "2" {}
  steps "in b" do
    it "2b" {}
  end
  it "3" {}
end

What steps should run in each case?

What effect should before/after blocks in "in b" have?

Conversely, there's already shared_steps and include_steps which work the other way around: set up the common parts in a shared_steps block, include_steps everywhere that they're needed.

[vasilakisfil]

Hi! In my opinion it would be nice if rspec-steps always preserved state of the outside block and previous "it" blocks of the same block. In your example "1" blocks should preserve the state that has been achieved until that moment (let it be "outside"). Similarly "1a" preserves the state of "outside" and "1".
"2" block preserves state "start" + "1" but not "1a" and in general anything inside a nested step defined in the same block but before "2".
Similarly, "3" block runs with a starting state "start" + "1" + "2".
I hope I made myself clear.