Closed MathieuLamiot closed 4 months ago
Updated the doc exxcept for the last item on the list. Do we have to list out each test and expected results ?
Updated the doc exxcept for the last item on the list. Do we have to list out each test and expected results ?
Listing all that would be overkill I think? What I had in mind was more of a quick test that we would have, to make sure the E2E setup is OK. I'm thinking maybe smoke tests? We could just say "run this command, after 1 minute, you should get this in the console and no errors. It means basic E2E setup is working". WDYT?
Okay, that makes sense. I'll update the doc with a smoke test and the expected result
We don't currently have anything to confirm if basic setup is fine or not, I created a draft PR https://github.com/wp-media/wp-rocket-e2e/pull/112, let me know if this is okay or we need to check for other features
What I would have in mind for a healthcheck:
@Khadreal Hello, I see this is in progress for more than a week. Are there any blockers or on-going discussions? Thanks
Looks good to me.
Update this doc: https://www.notion.so/wpmedia/Rocket-E2E-Test-Automation-using-Cucumber-Playwright-aecad10ae0c14a11aa609881a9d1230b?pvs=4
With details following the questions we had recently:
Maybe consider moving this documentation to a docs folder in the repo directly, to ease its maintenance?