Great content buddies, I have started using Playwright and I have integrated in CI, however I have two challenges: 1. It is always a challenge to automate production environment for examples if we have an e-commerce platform ww want to make sure that customers can place the orders seamlessly. How this can be done on production environment since we don't want to record dummy orders on prod. Note: There is no delete component 2. How to mitigate the failed step or test cases which cause Playwright to skip the all remaining test cases?
Thanks! Happy the webinar has been valuable. 💙 1) This case is a tricky one when there's no delete component. Maybe you could build in a switch in your application without cluttering your DB? But yeah if you want to test end-to-end you have to test end-to-end, so I'd vote for bringing in a deletion component. ;) 2) I'm not sure I understand this. If you're parallelizing your tests they should all be running independently. But if you go for sequential order I think it makes sense that the rest isn't running. It's hard to give guidance without knowing specifics. :)
1. Like for any true e2e tests you should have before or after hooks that run some form of cleanup or sanitization when there is a real database involved. This is especially true for when running in production. Your options are; use mocks, intercept requests, or run clean up after or before tests run.
2. Do you mean that in a given test it doesn't continue after a failure? Or for a spec with multiple tests that once a failure happens none of the other tests are run?
Great Webinar. Very useful !
Glad you think so!
Great content buddies, I have started using Playwright and I have integrated in CI, however I have two challenges:
1. It is always a challenge to automate production environment for examples if we have an e-commerce platform ww want to make sure that customers can place the orders seamlessly. How this can be done on production environment since we don't want to record dummy orders on prod.
Note: There is no delete component
2. How to mitigate the failed step or test cases which cause Playwright to skip the all remaining test cases?
Thanks! Happy the webinar has been valuable. 💙
1) This case is a tricky one when there's no delete component. Maybe you could build in a switch in your application without cluttering your DB? But yeah if you want to test end-to-end you have to test end-to-end, so I'd vote for bringing in a deletion component. ;)
2) I'm not sure I understand this. If you're parallelizing your tests they should all be running independently. But if you go for sequential order I think it makes sense that the rest isn't running. It's hard to give guidance without knowing specifics. :)
Thanks for reaching out here!
1. Like for any true e2e tests you should have before or after hooks that run some form of cleanup or sanitization when there is a real database involved. This is especially true for when running in production. Your options are; use mocks, intercept requests, or run clean up after or before tests run.
2. Do you mean that in a given test it doesn't continue after a failure? Or for a spec with multiple tests that once a failure happens none of the other tests are run?
@@modern_sapien second scenario you mentioned (spec that has several tests cases in test.describe when one failed remain test cases are skipped