blitzy alternatives and similar packages
Based on the "Testing" category.
Alternatively, view blitzy alternatives based on common mentions on social networks and blogs.
-
proper
PropEr: a QuickCheck-inspired property-based testing tool for Erlang -
bypass
Bypass provides a quick way to create a custom plug that can be put in place instead of an actual HTTP server to return prebaked responses to client requests. -
amrita
A polite, well mannered and thoroughly upstanding testing framework for Elixir -
power_assert
Power Assert in Elixir. Shows evaluation results each expression. -
shouldi
Elixir testing libraries with nested contexts, superior readability, and ease of use -
katt
KATT (Klarna API Testing Tool) is an HTTP-based API testing tool for Erlang. -
FakeServer
FakeServer integrates with ExUnit to make external APIs testing simpler -
Stubr
Stubr is a set of functions helping people to create stubs and spies in Elixir. -
mix_test_interactive
Interactive watch mode for Elixir's mix test. https://hexdocs.pm/mix_test_interactive/ -
mecks_unit
A simple Elixir package to elegantly mock module functions within (asynchronous) ExUnit tests using Erlang's :meck library -
test_selector
Elixir library to help selecting the right elements in your tests. -
factory_girl_elixir
Minimal implementation of Ruby's factory_girl in Elixir. -
toxiproxy_ex
ToxiproxyEx is an Elixir API client for the resilience testing tool Toxiproxy. -
ex_parameterized
This library support parameterized test with test_with_params macro. -
cobertura_cover
Output test coverage information in Cobertura-compatible format -
ex_unit_fixtures
A library for defining modular dependencies (fixtures) for ExUnit tests. -
ElixirMock
Creates clean, concurrent, inspectable mocks from elixir modules
Clean code begins in your IDE with SonarLint
Do you think we are missing an alternative of blitzy or a related project?
Popular Comparisons
README
Blitzy - A simple HTTP load tester in Elixir
Inspired by this post by Victor Martinez of WatchSumo.
% ./blitzy -n 100 http://www.bieberfever.com
Distributed Blitzy
It is way more fun to start distributed. Edit the provided config/config.exs
with whatever node name suits your fancy. This is optional, and you can stick to the provided one.
config :blitz, master_node: :"[email protected]"
config :blitz, slave_nodes: [:"[email protected]",
:"[email protected]",
:"[email protected]"]
Here, the master node is :[email protected]
; the rest are slave nodes.
Start up a couple of nodes, and name them accordingly. For example, here's how to start one of them:
% iex --name [email protected] -S mix
Now, when you run the the command
% ./blitzy -n 100 http://www.bieberfever.com
the requests will be split across the number of nodes you created, including the master node. Here's an example run:
17:03:30.600 [info] worker [[email protected]] completed in 5451.854 msecs
17:03:30.600 [info] worker [[email protected]] completed in 5258.639999999999 msecs
17:03:30.600 [info] worker [[email protected]] completed in 5272.281 msecs
17:03:30.600 [info] worker [[email protected]] completed in 5452.012 msecs
17:03:30.600 [info] worker [[email protected]] completed in 5258.318 msecs
17:03:30.600 [info] worker [[email protected]] completed in 5300.413 msecs
...
17:03:31.023 [info] worker [[email protected]] completed in 5653.303 msecs
Succeeded : 50
Failures : 0
Total time (msecs): 542665.9879999999
Avg time (msecs): 1629.6275915915912
17:03:31.024 [info] worker [[email protected]] completed in 5609.749 msecs
Succeeded : 50
Failures : 0
Total time (msecs): 485414.8010000001
Avg time (msecs): 1457.7021051051054
Building the Executable
mix escript.build