-
Notifications
You must be signed in to change notification settings - Fork 199
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
Add create-nightwatch docs. #156
base: versions/2.0
Are you sure you want to change the base?
Conversation
251a8b5
to
d4115b2
Compare
and answer a few questons. We'll setup everything for you based on your preferences. | ||
|
||
|
||
If you'd like to skip all the questions (we'd assume best defualts for you), you can use the above commands with `--yes` or `-y` flag: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
```suggestion
If you'd like to skip all the questions (we'd assume best defaults for you), you can use the above commands with `--yes` or `-y` flag:
|
||
##### 1) If you're in your existing project's root directory: | ||
|
||
<pre><code class="language-bash">npm init nightwatch -- --yes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this is necessary because it's not intuitive at all what all those defaults will be and what will happen. I think if users will use this tool, they will always want to go through the questions, which in my opinion are very sensible and the number is pretty low.
Also many questions aren't yes/no, such as JavaScript vs TypeScript. Does the answer yes means JS? Or the test runner (default / mocha / cucumber)?
So I think we should simply remove this completely.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about just generating the default Nightwatch config file for them if they use the --yes
option? The same config file which gets generated now when the users run their first test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On second thought, it wouldn't be a good idea to do so because we don't just generate the configuration file with this tool but also install all the required dependencies and if we just generate the same config file as we do now, we'd have to install a lot of unnecessary dependencies which is not a good idea at all.
|
||
#### Usage | ||
|
||
All you need to do is, run: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be really cool to have an animated gif that demo's the tool in action, such as the one in the schematics project or this video: https://vimeo.com/376838936
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[``](hi nama)
No description provided.