-
Notifications
You must be signed in to change notification settings - Fork 131
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
Build interactive configuration tool for populating .env properties #60
Labels
Comments
lenaorobei
added a commit
to lenaorobei/magento2-functional-testing-framework
that referenced
this issue
Mar 24, 2018
5 tasks
lenaorobei
added a commit
to lenaorobei/magento2-functional-testing-framework
that referenced
this issue
Mar 26, 2018
lenaorobei
added a commit
to lenaorobei/magento2-functional-testing-framework
that referenced
this issue
Mar 26, 2018
okolesnyk
added a commit
that referenced
this issue
Mar 29, 2018
#60: Build interactive configuration tool for populating .env properties
5 tasks
okolesnyk
added a commit
that referenced
this issue
Mar 30, 2018
Deliver changes from Contribution Day ### Fixed Issues (if relevant) 1. Resolve #56: Add "block" type to list of existing section element types 2. Resolve #57: Debug flag exists in robo generate:tests to print action sequence of test steps 3. Resolve #58: Allow browser type to be configured in env file 4. Resolve #60: Build interactive configuration tool for populating .env properties 5. Resolve #61: Validate build:project was run before attempting to generate tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently you're required to run build:project than manually configure the .env file through another editor. This could be wrapped in an interactive robo command: http://robo.li/getting-started/#io
User flow:
Validation on the inputs on these steps would also help detect issues with the setup. The system could also do a quick validation upon the configuration's input to verify if the environment exists and is working correctly.
The text was updated successfully, but these errors were encountered: