You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A button/wizard that spins up end-to-end QA automation for any web app.
Login with GitHub
Select a repository
Select test folder/pattern
Commit shortest.config.ts file to repo
Commit GitHub Action that runs these tests on every commit to main, pull request commit (booleans in UI?)
Next:
Automatic test suite generation (shortlist of typical user flows)
More options around config + GitHub action workflow
Why
We should ship this incrementally, and this would allow us to start building out a web app experience without hijacking the core shortest package. Over time, we can get smarter about generating tests and simplifying the "tests" that live within the repo. However, the tests should still live in the repo as that's the right place for tests to live – within version control, per commit, per PR, etc.
The shortest hosted service will be "smarter" than just running those tests. It could look at PRs and make suggestions by running tests and committing them to the codebase upon successful run (or upon the user confirming they want those added).
Example
No response
The text was updated successfully, but these errors were encountered:
What
A button/wizard that spins up end-to-end QA automation for any web app.
main
, pull request commit (booleans in UI?)Next:
Why
We should ship this incrementally, and this would allow us to start building out a web app experience without hijacking the core shortest package. Over time, we can get smarter about generating tests and simplifying the "tests" that live within the repo. However, the tests should still live in the repo as that's the right place for tests to live – within version control, per commit, per PR, etc.
The shortest hosted service will be "smarter" than just running those tests. It could look at PRs and make suggestions by running tests and committing them to the codebase upon successful run (or upon the user confirming they want those added).
Example
No response
The text was updated successfully, but these errors were encountered: