Open pcardosolei opened 2 years ago
Hey @pcardosolei, thanks for reporting. I'm still here, reviewing all of the issues and working hard on synpress@2.0.0
. I will make sure to fix most of the issues in upcoming release.
some alpha: https://github.com/orgs/Synthetixio/projects/14/views/4
Cheers, Jakub 🤝.
Hey
Thanks for the quick response. If you need help tell me. I can save a few hours of my week on in. Regards,
Hey @pcardosolei & @drptbl,
This is the exact behavior I want in my tests. Is there a workaround to get this done for the time being?
Hey @pcardosolei,
I'm happy to incentivise your work if you're willing to contribute to synpress.
Feel free to reach out to me on telegram: @DRPTBL
.
Your issue is still valid as synpress doesn't support cypress open
yet.
@drptbl i'm quite busy lately. We stopped using cypress + metamask or synpress at the moment on the cases we were using.
If i can give you a hand i will ping you.
Hello.
I'm using synpress as a plugin by adding it on the cypress configuration.
I'm using the following two commands local debug:
"cy:open": "CYPRESS_REMOTE_DEBUGGING_PORT=9222 cypress open"
dashboard is cool to run in my machine a single file.
CI/CD:
"cy:run": "CYPRESS_REMOTE_DEBUGGING_PORT=9222 cypress run --headed --browser chrome"
to work on the pipeline.
I have a test where it attempts to connect to the website where the success case is getting the signature accepted.
If i run the first command it automatically gets Metamask access and goes automatically to the signature request form. the second one goes though the Metamask access request and wait from the prompt and then goes to the signature request.
my workaround. i guess adding a env variable to control this would be ok.
I suppose the process is requesting Metamask access -> get accepted and then request the signature -> get accepted.
I'm not sure if this is a normal behaviour.
Feel free to request any information.