The most interesting parts from this video: 53:50 “Create an order” tests. 1:05:23 waitForResponse() instead of waitForTimeout(). 1:19:23 Tests from my Pet Project. Mobile app - Detox. AAA Pattern.
Don't listen guy in comments with "the most interesting parts from this video", full video is incredibly interesting !!! 🙂 Do not forget to click on thumbs up and subcribe.
thank you 🤜 it's extremely loooong so I decided to add that "most interesting parts" comment for the people who don't have 1.5h and still want to learn something new :)
Шеф, все круто, но у меня вопрос. Мы делаем ассерты на то, что локатор содержит текст. Но, если ассортимент изменился, названия футболок поменялись -> наши автотесты пошли по тому самому месту, о котором не упоминают в светских беседах? Не логичнее бы было найти цсс или икспас локатор и делать проверку, что этот локатор содержит текст? А в случае, если локатор указывпет на несколько элементов, по запустить innerText() локаторов в массив или стрим и там проверить?
да-да, не пережитки селениума, спасибо за таймкод)@@OleksiiVasylenko-r1j Я всегда стараюсь добавить айди либо test-id и по ним стучаться к элементам. Когда автоматизатором был, то просил разработчиков дать доступ к их коду и сам добавлял, потому что обычно легче самому добавить, чем ждать от них) P.S. буквально сегодня вижу в чате сообщение "ребят, кто поменял CARE та Care? тесты упали" - не надо завязываться на текст 🥲
Thanks for the new video, I have a question for you) Does it make sense to use test.describe method in playwright? In the real project you used this method, but when you wrote tests for online store you didn't.
Thanks for asking 👍 It's more like a code style or a personal preference. From my experience I would say that groupping tests with describe blocks makes sense when you have a lot of tests in 1 test file. Another option would be to just split big test files into a few smaller ones.
@@IlarionHalushka I don't know why, but when I post this comment on the POM lecture video, it doesn't post, so I'm trying here.) I was looking forward for this lesson, because it's a very interesting topic) I investigate a lot of articles, and asked questions on forums, but I still want to know your opinion about: - Where is better to write asserts, in a POM class, in a separate class only with asserts or directly write in tests ? - One person on the forum, advised me to write ONLY locators in the POM class, and to create a separate class "Steps" in which to write actions with locators from POM class (for example classes - "LoginPage" and "LoginSteps"), i.e. to divide business logic and locators, + sometimes business logic can require the participation of other pages, so it may be useful). - And also it is interesting about concept as Actors, is it worth to create a class with actors, to provide Declarative interface in tests, for example in "LoginSteps" class we have methods with Imperative interface, such as (enterEmail, enterPassword, clickLoginBtn), and in "LoginActor" class we can write a method with declarative interface such as - loginInSystem (which contains methods from LoginSteps class), and use it in tests. Is it better to use this option or write a declarative interface in LoginSteps initially? The topic is too big, so there are a lot of questions))) Hope that I formulated questions clear.
@@pavel_arabadzhy Ok, all questions totally make sense and I've been thinking about this for years. The answer to all 3 questions is - it doesn't matter :) It's just a code style preference. There is no right or wrong here. I feel like many people concentrate on engineering things which don't matter and don't bring any value. They want to build fancy test automation frameworks, use all possible patterns, build abstractions, etc. In my opinion, the most important questions are: Do autotests bring VALUE to devs/qa/company/product? Are the tests stable? Do we have CI job that runs tests on each Pull request?...
The most interesting parts from this video:
53:50 “Create an order” tests.
1:05:23 waitForResponse() instead of waitForTimeout().
1:19:23 Tests from my Pet Project. Mobile app - Detox. AAA Pattern.
Waiting for the next video from the best teacher, but first I need to complete this one!
thank you!
best student 🫡
Don't listen guy in comments with "the most interesting parts from this video",
full video is incredibly interesting !!! 🙂
Do not forget to click on thumbs up and subcribe.
thank you 🤜
it's extremely loooong so I decided to add that "most interesting parts" comment for the people who don't have 1.5h and still want to learn something new :)
@@IlarionHalushka even though it’s long it’s amazing happy to wait you are an amazing teacher
thank you! I really appreciate it!@@MaheshJoshi_wellington
🤩🤩🤩 Thank you so much for this amazing video 🤩
thank you))
thanks for the lesson Ilarion
thank you!
Respect. Thank you.
thank you 🤜
Шеф, все круто, но у меня вопрос. Мы делаем ассерты на то, что локатор содержит текст. Но, если ассортимент изменился, названия футболок поменялись -> наши автотесты пошли по тому самому месту, о котором не упоминают в светских беседах? Не логичнее бы было найти цсс или икспас локатор и делать проверку, что этот локатор содержит текст? А в случае, если локатор указывпет на несколько элементов, по запустить innerText() локаторов в массив или стрим и там проверить?
Ведь при таком подходе, мне кажется, будет легче осуществлять поддержку POM? Или это пережитки селениума во мне говорят?
1:15:00 - вот я об этом имел в виду, да)
да-да, не пережитки селениума, спасибо за таймкод)@@OleksiiVasylenko-r1j
Я всегда стараюсь добавить айди либо test-id и по ним стучаться к элементам. Когда автоматизатором был, то просил разработчиков дать доступ к их коду и сам добавлял, потому что обычно легче самому добавить, чем ждать от них)
P.S. буквально сегодня вижу в чате сообщение "ребят, кто поменял CARE та Care? тесты упали" - не надо завязываться на текст 🥲
@@IlarionHalushka а можно ли toLowerCase-нуть тексты, чтобы CARE/care/Care воспринимались одинаково?
amazing
thank you!!
Thanks for the new video, I have a question for you)
Does it make sense to use test.describe method in playwright? In the real project you used this method, but when you wrote tests for online store you didn't.
Thanks for asking 👍
It's more like a code style or a personal preference.
From my experience I would say that groupping tests with describe blocks makes sense when you have a lot of tests in 1 test file.
Another option would be to just split big test files into a few smaller ones.
@@IlarionHalushka I don't know why, but when I post this comment on the POM lecture video, it doesn't post, so I'm trying here.)
I was looking forward for this lesson, because it's a very interesting topic) I investigate a lot of articles, and asked questions on forums, but I still want to know your opinion about:
- Where is better to write asserts, in a POM class, in a separate class only with asserts or directly write in tests ?
- One person on the forum, advised me to write ONLY locators in the POM class, and to create a separate class "Steps" in which to write actions with locators from POM class (for example classes - "LoginPage" and "LoginSteps"), i.e. to divide business logic and locators, + sometimes business logic can require the participation of other pages, so it may be useful).
- And also it is interesting about concept as Actors, is it worth to create a class with actors, to provide Declarative interface in tests, for example in "LoginSteps" class we have methods with Imperative interface, such as (enterEmail, enterPassword, clickLoginBtn), and in "LoginActor" class we can write a method with declarative interface such as - loginInSystem (which contains methods from LoginSteps class), and use it in tests. Is it better to use this option or write a declarative interface in LoginSteps initially?
The topic is too big, so there are a lot of questions))) Hope that I formulated questions clear.
niiiiice, love the questions!!!@@pavel_arabadzhy
@@pavel_arabadzhy
Ok, all questions totally make sense and I've been thinking about this for years.
The answer to all 3 questions is - it doesn't matter :) It's just a code style preference. There is no right or wrong here.
I feel like many people concentrate on engineering things which don't matter and don't bring any value. They want to build fancy test automation frameworks, use all possible patterns, build abstractions, etc.
In my opinion, the most important questions are:
Do autotests bring VALUE to devs/qa/company/product?
Are the tests stable?
Do we have CI job that runs tests on each Pull request?...
Again, love the questions. The next video I publish will be targeting guys like you.
(Not a lesson but a video)@@pavel_arabadzhy
А Allure report будет???
step by step