-
-
Notifications
You must be signed in to change notification settings - Fork 200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Expose scenario states #163
Comments
Good idea. I need to extend the admin api with some get request to retrieve the state from a certain scenario. Also add this logic to the fluent interface. |
Hello @benjamin-bader, I've added some functionality in this branch, you can already take a look how it can be used as you proposed here: |
Oh, cool! I was going to try my hand at this, but you've beaten me to it. Thank you for taking the effort! |
OK, I'll change the code and create a new NuGet in some time... |
I'd like to be able to ask the server what the current state is for a given feature, for example to concisely verify that all expected requests were received, e.g.
One could get the same effect today by groveling through the LogEntries, but this is tedious and duplicates the logical chain set up by the scenario itself.
The text was updated successfully, but these errors were encountered: