At the moment, the semantics of subgroups are pretty unclear. describe or steps inside of a steps block doesn't make sense to do the normal rspec behavior - it will work but be confusing. Fastest solution is to have describe just fail and point to this issue, better is maybe to do something like branching?
Normal describe blocks being able to take the current state, see examine it, and then let steps continue might be good (i.e. resume test independence, but with the prequel steps being treated as a before :all of the subgroup)
Sub-steps treated as a branch-point (try it this way, try it that way) would also be good, especailly if prequel steps could be treated, again, as a before :all.
Significant issue with both approaches: non-variable state. Thinking of database, selenium browsers as specific examples. Who knows what else?
At the moment, the semantics of subgroups are pretty unclear. describe or steps inside of a steps block doesn't make sense to do the normal rspec behavior - it will work but be confusing. Fastest solution is to have describe just fail and point to this issue, better is maybe to do something like branching?
Normal describe blocks being able to take the current state, see examine it, and then let steps continue might be good (i.e. resume test independence, but with the prequel steps being treated as a before :all of the subgroup)
Sub-steps treated as a branch-point (try it this way, try it that way) would also be good, especailly if prequel steps could be treated, again, as a before :all.
Significant issue with both approaches: non-variable state. Thinking of database, selenium browsers as specific examples. Who knows what else?