Skip to content
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

"Headless" mode for the Spec previewing and editing client #596

Open
jeremydmiller opened this issue Nov 15, 2016 · 4 comments

Comments

Projects
None yet
3 participants
@jeremydmiller
Copy link
Member

commented Nov 15, 2016

Now that we have the Fixture overrides and export working, what if there was a mode in st that allowed you to run the Storyteller client against only the Fixture markdown files without the backend system going at all? Might be a huge advantage for testers or even devs

@mtscout6

This comment has been minimized.

Copy link
Member

commented Nov 15, 2016

Is this to make sure it can be parsed? Not sure I follow.

@CNBoland

This comment has been minimized.

Copy link

commented Nov 15, 2016

If I follow correctly, that would allow testers to write tests in markdown rather than app code?

@jeremydmiller

This comment has been minimized.

Copy link
Member Author

commented Nov 15, 2016

@mtscout6 I haven't forgotten the story about validating all the specs and that one's still open and should get done for 4.0 by the beginning of the year.

What I'm after is being able to completely use the UI client for previewing or authoring specifications without having to actually run the system under test or any of the .Net testing code. We'd need to disable or better yet hide any commands that involve the backend.

I was thinking that this mode could be very valuable early on in the project or when a system isn't easy to bootstrap locally.

@mtscout6

This comment has been minimized.

Copy link
Member

commented Nov 15, 2016

Ok, so this would allow you to write the test and later on to generate the C# fixtures based on them? All without the system under test being in a working state. I can dig that.

@jeremydmiller jeremydmiller modified the milestone: 4.0 Dec 4, 2016

@jeremydmiller jeremydmiller modified the milestones: 4.0, 4.1 Jan 5, 2017

@jeremydmiller jeremydmiller modified the milestone: 4.1 Mar 7, 2017

@jeremydmiller jeremydmiller added this to the 4.5.0 milestone Oct 4, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.