-
-
Notifications
You must be signed in to change notification settings - Fork 270
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
Feat/suite desktop core/convert unaquired device #16603
Feat/suite desktop core/convert unaquired device #16603
Conversation
rename refactor locator @deviceStatus and few cy tests split test to viewOnly enabled and false
🚀 Expo preview is ready!
|
81ca301
to
4df18e2
Compare
fixes locators, leaves the original one in place until we get rid of cy
4df18e2
to
d243c6a
Compare
@@ -6,7 +6,7 @@ import { step } from '../common'; | |||
|
|||
export class DevicePromptActions { | |||
readonly confirmOnDevicePrompt: Locator; | |||
private readonly connectDevicePrompt: Locator; | |||
readonly connectDevicePrompt: Locator; |
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 want to expect the text in the locator on test level
await test.step('Steal Bridge session', async () => { | ||
const bridge = new BridgeTransport({ messages, id: 'foo-bar' }); | ||
await bridge.init(); | ||
const enumerateRes = await bridge.enumerate(); | ||
if (!enumerateRes.success) return null; | ||
await bridge.acquire({ | ||
input: { path: enumerateRes.payload[0].path, previous: null }, | ||
}); | ||
}); |
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.
copy pasta from cypress suite
better logging of test steps
77f5e6f
to
a7b9e6d
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.
Once we convert all cypress test using these locators, we will simplify that to one statically named locator.
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.
Once we convert all cypress test using these locators, we will simplify that to one statically named locator. It is not good practice to build your expects around internal state and values of the UI. That way the internal state can be correct but the information shown to user can be still incorrect and test falsely passes.
|
||
test( | ||
'Overtake session by opening suite new tab', | ||
{ tag: ['@webOnly'] }, |
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.
Mixing electron and web would complicate our CI setup. I don't think it is worth the value. Let me know what you think.
And I assume two desktop apps running on one system is not a thing.
Description
Converts to PW test file unaquired-device
Renamed to multiple-sessions as I added a test that works with two tabs (something that playwright can do :) ). Feel free to challenge the renaming.
Adds bunch of verification. We found out an issue with Stew 👍
Splits test to view only enabled and disabled
Related Issue
Resolve 15606
Screenshots:
Desktop: https://app.currents.dev/instance/OVrwYg0tq2P9Ps6D
Web: https://app.currents.dev/instance/44AQxvrBBBBTzwnx