switch out gherkin for pytest
kapilt opened this issue · comments
gherkin is a bit slow and its forking for each test, converting the suite to pytest would let us run probably quite a bit faster and with more options on test control
Currently, using tox to run each feature one-by-one to make it slightly easier to debug.
In the future, it will be a single behave step. Currently working on the next release and seeing this.
15 features passed, 0 failed, 5 skipped
631 scenarios passed, 0 failed, 344 skipped
1373 steps passed, 0 failed, 1018 skipped, 0 undefined
Took 0m1.986s
Behave on the entire feature suite will take about 2 seconds.
This is without any AST optimization. A lot of empty nodes are visited.