-
Notifications
You must be signed in to change notification settings - Fork 186
[POC][tests-only] e2e tests with Playwright only #12941
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
1facfa0
to
9b2c634
Compare
@Ashim-Stha Could you edit the PR title to something like this? |
done 👍 |
9b2c634
to
c242bfc
Compare
f52c40f
to
751f68f
Compare
@LukasHirt Could you review this one and check if this is how we want to have the tests? |
136e5fb
to
edc5302
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made a few comments related to readability of the test "scenario".
What sort of people do we want to be able to read and comprehend what the test suite is testing?
Do we want non-technical people to be able to put together a test scenario (using existing available steps) that would demonstrate some expected behavior?
Or is the test suite to be used just by technical staff who are doing SW development and test development?
Answers to these questions might help answer what format/framework is best for implementing the test suite.
) | ||
await ui.LogOutUser(actorsEnvironment, 'Alice') | ||
|
||
expect(await ui.isAbleToEditFileOrFolder(actorsEnvironment, 'Brian', 'myfolder')).toBeFalsy() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This implements the scenario step:
Then "Brian" should not be able to edit folder "myfolder"
A technical user who knows coding can read the line of code and work out what is being expected. So the choice of format depends who the "target audience" is for the test suite.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
edc5302
to
f935551
Compare
Signed-off-by: Ashim Shrestha <[email protected]>
f935551
to
971cce6
Compare
|
@LukasHirt @deyankiteworks Please feel free to merge this if everything is ok from your side |
Description
Rewrite the old Cucumber test from
tests/e2e/cucumber/features/shares/internalLink.feature
with a new Playwright test attests/spec/internalLink.spec.ts
Related Issue
#12938
Run test
To run test locally in
chromium
inheaded
mode