Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upElixir as a test scripting language #355
Comments
|
I'm not sure if I see a question here :) "Tests" in Tsung are declarative and expressed in XML, that being said, you can create a XML generator using Elixir. But that raises the question of what could be gained by that. There is currently no direct way to provide the declaration in another format, but that could be a doable project, if you like to contribute. Does this answer your question? |
|
We could use a generator, but then we have two sources. XML is prohibitive and FP itself is declarative. I think they'd be a preference for scripting (Locust, for example gets a lot of traction) and complex tests are difficult to read in XML. But I know it was a big ask. I'll do a crash course in Erlang and see what I can do. I was also thinking we could tail some logs or something and use InfluxDB as a datasource for real time graphing in Grafana. |
|
You're parsing different protocols maybe start off with HTTP? |
|
I understand the motivation, and I see a similar benefit from having a more dynamic way of programming a test case. But unfortunately that might be a significant undertaking from what I can tell :( |
We've started an Elixir book group in a large British media organisation. We are trying to get people using Elixir. Tsung appeals obviously because of BEAM processes and the ability to scale (many machines). We'd like to be able to write our tests in Elixir and not XML. Not familiar with Erlang, else I'd have a go myself.