What are the best practices of automation testing with Java testing framework Selenide?

Lately i have been doing research on the best practices of automation testing with Java testing framework Selenide. If anyone knows please let me know.

Seledine was created to simplify the writing of UI tests.

And that is true, the framework is really good for UI testing, but it doesn’t handle well other types of testing. So the best practice is to use this framework only for GUI regression or GUI smoke testing. In such a way Seledine shows its full capacity and advantages over the rest:

  1. Convenient API to accelerate project start.
  2. No ajax and timeouts problems. Often the tests fail just before the element on the page is loaded. Selenide solved these issues, thus you can concentrate on business logic instead.
  3. Automatic screenshots. No need to configure anything, you always get a screenshot after a test run.
  4. Simplicity of use. Selenide is clear and simple even for people who are just beginning to automate or have not seen this framework before.

Hope you’ll find this answer useful :slight_smile: