Wrap E2E wdio code in our own class - Follow-up from "test: add e2e test framework"
The following discussions from !1443 (merged) should be addressed:
-
@ghosh-abhinaba started a discussion Open question: Do we want to wrap wdio methods in other factory function like
getWorkbench
. The advantage is if we change the tool (from wdio -> playwright for say), we don't have to update the tests rather the factory function instead.We can revisit this later as well. Not a blocker.
-
@mlapierre started a discussion: thought (non-blocking): I wonder if we should wrap some of the wdio code in our own class so we could write something like:
await prompt.waitToContain('URL to Gitlab instance'); await prompt.confirm();
But that's a possible enhancement for another MR.