So I've written a good amount of scripts using Capybara with Selenium Web-driver. It's going well but my automation tests feel more like step by steps scripts, without much Object Oriented design or foresight.
I've read about the Page Object Model with Selenium and it makes sense...however most examples are in Java (Which makes sense because Java+Selenium is so common) but also the examples are usually simple in a sense that Page Object Model makes sense with that sort of tests.
I'm in a predicament, because the web application I want to implement Page Object Model is unique in that it's multiple steps (Think each page having a new form and new user type). So there isn't really a place where something is "commonly" used among multiple parts of the app. (Besides maybe referring to a "Title" or "Username" occasionally. It's quite a complicated app.
In something like this does POM make sense? If so how would you set it up? Make each step it's own method perhaps (Which is essentially a gigantic form, sometimes even 10-15 inputs). This feels a bit strange because if I'm actually making this single step a method, then I'm passing a huge amount of parameters to do the form.
What makes sense here? Is POM even a good idea if there isn't really much duplication when doing a "happy-path/main functionality" run of the web application.