-
Notifications
You must be signed in to change notification settings - Fork 4
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
automatic and interactive creation of new automation starter projects #242
Comments
Selenium tests cannot run locally on a Codespaces instance because it does not support installation of Googe Chrome Anyway, it would be useless, because developing such tests requires openning DevTools and experimenting with XPath expressions and seeing how a test runs, or doesn't, is also important. Still, it is possible to run Selenium tests from Codespaces in remote mode, e.g. against a SauceLabs account, or have a Grid running on local machine exposed via TailScale (or some other VPN -- see https://docs.github.com/en/codespaces/developing-in-a-codespace/connecting-to-a-private-network) |
Appears that Playright is supported... |
Openning a Codespace in Jetbrains Gateway fails: |
For faster docker builds -- https://www.docker.com/products/build-cloud/ and apply for a license here: https://www.docker.com/community/open-source/application/ |
depends on #246 |
Current State
Currenly, creating an automation project comprises several manual steps:
qa-testing-archetype
maven archetype as desacribed in https://qa-automation-starter.aherscu.dev/qa-testing-parent/qa-testing-archetype/index.htmlHow to make it better
Provide a Create New Project somewhere on the landing page to run above steps while prompting the user for
groupId
,artifactId
andversion
. The newly generated repository should initiate a preconfigured codespace environment with all project's required features for VSCode and for running the automation examples, e.g. Selenium, Appium, RabbitMQ, etc.The text was updated successfully, but these errors were encountered: