All posts (4)
One of the challenge for start-up or any new project is to reduce amount of work yet to deliver full-featured product. Agile methodologies address this challenge on project management level. Let’s discuss one more approach to address it on architecture level: UI-first development.
Recently I was asked how to start with testing UI before backend is completed. It depends on the product a lot. But when we’re talking about web, it is often not clear how the final solution should look like and behave. If so, it is not reasonable to spend much time writing UI tests using tools like Selenium before the first prototype is ready. It is not reasonable to write a presentation layer and, in some cases, a business logic on server side before it is clear what kind of data is required for UI.
Selenide is nice wrapper around selenium web driver allowing to simplify writting UI tests with Selenium.
Some of the cook features are:
- jquery-like selector syntax, e.g.
- Automatic screenshots on assertion failure
- Easy starting Selenium WebDriver
- And others
So, let’s write some tests on selenide and make it run from maven in a normal browser or in headless mode.