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
I think a button to run a test in a headed browser from the playwright ui would be a great improvement.
Example
In the config file a project can be marked as default.
In the playwright ui a new button can be clicked to run: playwright test --project='<default from config>'-g '<name>' (name is replaced with the actual test name)
(Optional) The test can be debugged and if it passes in the headed browser the test can be marked as passed in the ui.
It could be placed here:
Motivation
Ever since the ui mode has been released my workflow has looked like this:
Use UI to run all test locally. (Terminal 1)
Check failing tests and fix obvious problems.
Go to file for failed test.
Copy name from file.
Run playwright test --project=chromium -g '<name>' (Terminal 2)
Debug the test.
Repeat 3-7 for each failed test.
I feel like having the option to just do steps 3-5 right from the failed test in the ui could be a major help.
The text was updated successfully, but these errors were encountered:
馃殌 Feature Request
I think a button to run a test in a headed browser from the playwright ui would be a great improvement.
Example
playwright test --project='<default from config>'-g '<name>'
(name is replaced with the actual test name)It could be placed here:
![image](https://private-user-images.githubusercontent.com/38015558/340941931-e8dd7eab-8940-46b6-8d65-11b573dd0b00.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk3NDIwNTcsIm5iZiI6MTcxOTc0MTc1NywicGF0aCI6Ii8zODAxNTU1OC8zNDA5NDE5MzEtZThkZDdlYWItODk0MC00NmI2LThkNjUtMTFiNTczZGQwYjAwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MzAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjMwVDEwMDIzN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTkzNzNhMjg3Y2IxYzQ4MWQ4OGQ2MGI4YTc1NTVjZmQ2NjgxMDhlMTE3ZTI4MjMzODYwZGI3YmQ1NGZhMTc4MmMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.ECshIZtoadmkIaX50NgstFFi--qSLtr93RYUY0XmBdw)
Motivation
Ever since the ui mode has been released my workflow has looked like this:
playwright test --project=chromium -g '<name>'
(Terminal 2)I feel like having the option to just do steps 3-5 right from the failed test in the ui could be a major help.
The text was updated successfully, but these errors were encountered: