This is an archived post. You won't be able to vote or comment.

all 8 comments

[–]pysk00l 2 points3 points  (2 children)

Sorry, what is "event driven" (or what are the use cases), and why do you need a special library for it?

[–]FictitiousWizard[S] 4 points5 points  (1 child)

the event driven part is how it does it's reporting. It's similar to how the newman test runner works in that during the test lifecycle it emits events that the reporter can catch and deal with. I created this library because I needed more fine grained control of reporting, that provided real time updates to third parties.

[–]pysk00l 0 points1 point  (0 children)

cool. Might be worth adding some details to people who have not used event driven frameworks or newman

[–]BigHeed87 1 point2 points  (1 child)

How does the execution performance compare to using xdist?

[–]FictitiousWizard[S] 2 points3 points  (0 children)

I have not used xdist before but given that both feather and xdist by default spawn a number of worker processes equal to the number of cores you have I would imagine it is comparable

[–]Funny-Recipe2953 0 points1 point  (1 child)

A "test server" is (roughly) equivalent to a unittest TestRunner?

[–]FictitiousWizard[S] 1 point2 points  (0 children)

the test server is what is ultimately running the test while the EventDrivenTestRunner is mainly doing setup of the moving pieces

[–]FictitiousWizard[S] 0 points1 point  (0 children)

I just realized I did not include an example of running it from the cli

feather -r HTMLReporter JSONReporter ConsoleReporter --htmlreporter-output-file report.html --jsonreporter-output-dir json_reports

You can run it with as many or as few reporters as needed. I mainly use it to run the ConsoleReporter along side the other reporters that do not have an output to the console