akka-http and selenium

[Anton Kulaga]

Hi all,

I wonder, are there any examples of apps with Selenium tests together with akka-http and scalatest 3.0.x?

[Rafał Krzewski]

Why would Selenium tests of application using akka-http be different from tests of application using any other server-side stack?

Cheers,

Rafał

[Anton Kulaga]

They should not I am just curious: there is a section of testing with browser in Play docs ( https://www.playframework.com/documentation/2.4.x/ScalaFunctionalTestingWithScalaTest#Testing-with-a-web-browser ), maybe somebody wrote a similar example about testing akka-http with browser

--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to a topic in the Google Groups "Akka User List" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/akka-user/GiwiOBvh33g/unsubscribe.
To unsubscribe from this group and all its topics, send an email to akka-user+...@googlegroups.com.
To post to this group, send email to akka...@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

--

Best regards,
Anton Kulaga

[Rafał Krzewski]

Oh, I see. OneServerPerSuite / OneServerPerTest traits must be really handy. Providing similar helpers for testing akka-http would be hard, because Play is a framework that mandates a well defined entry point and configuration strategy, whereas akka-http is not.

Cheers,

Rafał

[Johannes Rudolph]

Hi Rafał,

On Monday, August 24, 2015 at 3:49:57 PM UTC+2, Rafał Krzewski wrote:

Oh, I see. OneServerPerSuite / OneServerPerTest traits must be really handy. Providing similar helpers for testing akka-http would be hard, because Play is a framework that mandates a well defined entry point and configuration strategy, whereas akka-http is not.

I wonder what you mean exactly? Maybe you mean that spray/akka-http doesn't really promote a "convention over configuration" approach to a degree that many modern web frameworks do. But that doesn't mean that there are no entry points or best practices upon which you could build similar testing functionality. It may mean that you need to be a bit more explicit about what you are currently testing and where to find the application components.

Or am I missing something?

Johannes