Dive into the world of Selenide and elevate your UI testing game! 
Join Andrei Solntsev as he demonstrates how to craft concise, readable, and stable UI tests using Selenide. Discover popular features like screenshots, reports, file downloading, and more—all the essentials you need without the hassle of writing them manually.
Still not registered? Hurry up and grab your free tickets: Register Now!
If you’re ready for the session, feel free to drop your questions in the thread below 
Hi there,
If you couldn’t catch the session live, don’t worry! You can watch the recording here:
Here are some of the Q&As from this session:
One of the things that I have encountered with Selenium tests is the flakiness associated with dynamic web elements? How does Selenide solve the flakiness issue for complex test scenarios?
Andrei Solntsev: Selenide handles the flakiness issue by providing built-in smart waiting mechanisms. It automatically waits for elements to be in the desired state (e.g., visible, clickable) before interacting with them, which significantly reduces the chances of tests failing due to timing issues with dynamic elements.
How can you make tests not be dependent one to another?
Andrei Solntsev: To ensure that tests are not dependent on one another, it’s important to design each test to be self-contained. This can be achieved by properly setting up and tearing down the test environment before and after each test. Selenide supports this by offering easy-to-use setup and cleanup methods, ensuring that each test starts from a consistent state.
How would you compare the difficulty in automating mobile apps vs web apps?
What tips do you have for beginners to start writing automated tests with Selenide?
What are the steps to set up Selenide for automating tests in a Java project?
Is Selenide an IDE?
How can we start using this? Is there an intro/setup guide somewhere?
How does Selenide simplify handling dynamic content and AJAX in automated tests for web applications?
What are some best practices for writing efficient tests with Selenide?
What is the best approach for testing native apps using BDD framework?
How can you make tests not be dependent one to another?
Andrei Solntsev: To ensure that tests are not dependent on one another, it’s important to design each test to be self-contained. This can be achieved by properly setting up and tearing down the test environment before and after each test. Selenide supports this by offering easy-to-use setup and cleanup methods, ensuring that each test starts from a consistent state.
What features of Selenide make it a suitable choice for writing automated tests for both mobile and web applications?
What is a good target for code coverage?
What are the steps to set up Selenide for automating tests in a Java project?
How would you compare the difficulty in automating mobile apps vs web apps?
How much coding knowledge is needed to use selenide?
does it support auto healing ?
Are there effective tools (or best practices) to help with reducing wordiness and complexity in the automated test scripting using Selenide?
