From what I have read about functional programming, it is considered to be more concise, more testable, and have fewer side effects. Would it be good to use for UI test automation?

Context: I am working in protractor with JavaScript and JavaScript supports functional programming concepts to an good extent. So I explored and experimented with concepts like first class functions and iterators, and functons like map, reduce, and filter, but I could not get it to a meaningful state in the context of UI automation. Does anyone have experience using it with Protractor or another UI test automation framework who could share some insights on using a more functional approach compared to OOP (as page objects pattern in selenium world) or a procedural approach.

Expectation: I would like some code examples with a few typical automation use cases to explain it in the automation context, as opposed to generic programming scenarios. I would also like an explanation of how it can improve the code for test automation; my primary design goals are maintainability, code reuse, modifiability, flexibility, and faster execution.

Example: To give an concrete typical scenario, in UI automation we need to interact with UI Grid and verify the content from an specific row and column based on some condition, and verify it with some expected values.

From what I have read about functional programming, it is considered to be more concise, more testable, and have fewer side effects. Would it be good to use for UI test automation?

Context: I am working in protractor with JavaScript and JavaScript supports functional programming concepts to an good extent. So I explored and experimented with concepts like higher order functions,immutability,pure functions,no side effects and functors like map, reduce, and filter, but I could not get it to a meaningful state in the context of UI automation. Does anyone have experience using it with Protractor/nightwatch or another javascript based UI test automation framework who could share some insights on using a more functional approach opposed to Object oriented or procedural approach.

Expectation: It would be great if someone can share some code examples with a few typical automation use cases to explain it in the automation context, as opposed to generic programming scenarios. Also some insights on how it can improve the code for test automation; my primary design goals are maintainability, reusability and readability.

Example: To give an concrete typical scenario, in UI automation we need to interact with UI Grid and verify the content from an specific row and column based on some condition, and verify it with some expected values.

As I read about functional programming, it is considered as more concise, testable and with less side effects.I am wondering if using it, will be good idea for UI test automation as well???

Context: As I am working in protractor with JavaScript and JavaScript supports functional programming concepts up to an good extent.So I explored and experimented with concepts like first class functions and iterators and functons like map, reduce and filter but could not get it to a meaningful state in UI automation context,so I am wondering if somebody having experience using it with protractor or other UI test automation framework and would like to share some insights on using more Functional approach compared to OOP(as page objects pattern in selenium world) or procedural approach..

Expectation: I would really appreciate if someone having this experience ,provide small code examples with few typical automation use cases to explain it in the automation context..as opposed to generic programming scenarios ,stating how it can improve the code for test automation where maintainability, code reuse, modifiability  , flexibility  , faster execution are primary design goals by keeping it DRY.

Example To give an concrete typical scenario, in UI automation we need to interact with UI Grid and verify the content from an specific row and column based on some condition...and verify it with some expected values.

From what I have read about functional programming, it is considered to be more concise, more testable, and have fewer side effects. Would it be good to use for UI test automation?

Context: I am working in protractor with JavaScript and JavaScript supports functional programming concepts to an good extent. So I explored and experimented with concepts like first class functions and iterators, and functons like map, reduce, and filter, but I could not get it to a meaningful state in the context of UI automation. Does anyone have experience using it with Protractor or another UI test automation framework who could share some insights on using a more functional approach compared to OOP  (as page objects pattern in selenium world) or a procedural approach.

Expectation: I would like some code examples with a few typical automation use cases to explain it in the automation context, as opposed to generic programming scenarios. I would also like an explanation of how it can improve the code for test automation; my primary design goals are maintainability, code reuse, modifiability, flexibility, and faster execution.

Example: To give an concrete typical scenario, in UI automation we need to interact with UI Grid and verify the content from an specific row and column based on some condition, and verify it with some expected values.