Suggestion for tackling dynamic content when doing visual testing: Use browser clock and freeze the browser state
@CowboyCoder21
9 ай бұрын
Loved the screenplay solution, anytime I'm developing a solution I always abstract away the library/driver I'm using for various reasons.
@test-automation-experience
9 ай бұрын
Did you already try Screenplay?
@bunyaminmete5468
Жыл бұрын
hey, how did you handle 2FA?
@test-automation-experience
Жыл бұрын
If 2FA was possible to automate then it wouldn't serve it's purpose. It was a manual step. We put it in place until we could find a programmatic solution.
@TOGACLAN
Жыл бұрын
Interesting conversation on where assertions should be and I'm glad to see I am not the only automation engineer conflicted over it. Currently, if an assertion is commonly used, I put it inside a pageObject.verifySomethingInPlainEnglish() method and assert it there. If it is something for a specific edge case, I will assert it in the test by using an exposed locator. I like what Pandy said about having page object method to get the state of an element and then assert that in the test as well. That could work for me. Regardless, good discussion :)
@test-automation-experience
Жыл бұрын
The latter is the better approach in my opinion. Keeps separation of concerns more clear
Пікірлер: 7