is there a way to execute some cleanup logic after a specification (test case) has finished.
The TearDown method of a Fixture will not help here because it is called too early. My specification consists of sections of several Fixtures where the first Fixture will setup some data and then some logic is executed from another Fixture. Only after all fixture code has finished should the set up data from the first running fixture be cleaned up.
I was thinking about some lifecycle event handlers in the Fixture class like OnSpecificationFinished() in addition to the already existing TearDown().
Obviously there currently is no such method. Is there another way to achieve something similar or is this a good topic for a feature request ;-) ?
dotnet storyteller command? Like dotnet storyteller —timeout #?
@jeremydmiller i have been looking at the code for a day or two, and i think that I have misunderstandings about the role of the IGrammar method on a fixture.
I am using storyteller to test the validity of a system installation (smoke test), but have a variable number of configurations during install that would effect which subsystems are running and require testing. So I was thinking that the I could create a method that created different Facts based on what we see in the installed configuration files. But I think by doing this, I am bumping elbows with the logical separation of Fixture from Specification and execution contexts. I see the the this.Context object which exposes services to my fixutres is not yet defined when the function is executed.
So my question, am I doing something completely not intended or is this kind of what you were thinking when you allowed dynamic IGrammar generation? And a follow up, if it was the design idea behind the IGrammar methods, is there an obvious way i am missing to get service injection at method execution time (since the generated grammars are executed later)?
Fixture.Context would only be available at the time the specification is being executed
