You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would awesome to have a functionality similar to the ExUnit tags. Especially for the suppression of the logs generated in the tests.
@tag :capture_log
it "should forward the error result and stop" do
#...
do
It would be useful for cases like this one, where ran three tests successfully but the first one is showing a ugly log.
.2017-10-11 14:46:57.783 nonode@nohost pid=<0.30.0> : Process #PID<0.576.0> raised an exception
** (RuntimeError) crash_test
spec/orders_service/fsm/recipient_spec.exs:683: anonymous fn/0 in (....)
..
This functionality already exists and is not documented correctly? or could be added in a near future?
A function capture_log already exists, but the purpose is different.
The text was updated successfully, but these errors were encountered:
Hi, @ever-cifuentes-globant !
ESpec has a different notation for tags (see (Context blocks and tags)
[https://github.com/antonmi/espec/blob/master/README.md#context-blocks-and-tags])
Idea of :capture_log tag is awesome! ESpec definitely needs such functionality!
This seems to be related.. I also found this kind of warnings related to the coverage, Again, it would be awesome to suppress those kind of warnings and have a nice and green tests executed.
...WARNING: Deleting data for module 'Elixir.ProcessQueue' imported from
["/path/to/my/project/process_queue/Elixir.ProcessQueue.coverdata",
"/path/to/my/project/process_queue/Elixir.ProcessQueue_meck_original.coverdata"]
It would awesome to have a functionality similar to the ExUnit tags. Especially for the suppression of the logs generated in the tests.
It would be useful for cases like this one, where ran three tests successfully but the first one is showing a ugly log.
This functionality already exists and is not documented correctly? or could be added in a near future?
A function
capture_log
already exists, but the purpose is different.The text was updated successfully, but these errors were encountered: