collaboration request

[kouk]

Hello,
I've been maintaining some step libraries among which is a sub-library that uses pexpect to test CLI behavior. If you would like me to contribute the code towards helping this project's development let me know.
Cheers..

[kouk]

See here in particular: https://github.com/longaccess/longaccess-behave/tree/master/behave_cli/expect

[jenisys]

I will look over it during the next weekend.
I have used pexpect in the past.

While I have a working prototype, I have not released it yet or pushed it to the repository, because there are more things to do. The current state is basically a cleaned up and extended "behave4cmd0" module with a partial test suite to ensure that the steps are working as expected.

[jenisys]

Mmh, I have problems accessing your repository on Github (using the URLs from above).

[kouk]

oops sorry. the urls pointed to a private repo. I published the code to a public repo and updated the urls in the comments.

[kouk]

and here's an example scenario: https://github.com/longaccess/longaccess-client/blob/master/features/login.feature

[jenisys]

Works now. I can access the repositories.

[jirutka]

While I have a working prototype, I have not released it yet or pushed it to the repository, because there are more things to do. The current state is basically a cleaned up and extended "behave4cmd0" module with a partial test suite to ensure that the steps are working as expected.

It’s almost 3 years since you wrote that. If you would have pushed what you had (even unfinished), I bet that someone would implement the rest and it would be ready these days. But now we have still nothing. :(

Could you please push what you have to the repository, so we can continue with the work instead of wasting time with reimplementation what you’ve already done?

[fkromer]

@jirutka As another 3 months passed by... are there alternative packages with BDD testing suited for CLA testing.

[jenisys]

The small brother "behave4cmd0" for it is currently bundled with behave. See "behave4cmd0" subdirectory. It is used by behave to test itself. See if this is sufficient for you current use case. Otherwise, I plan to release/publish this repository soon.

[fkromer]

Thanks a lot for the hint. I am already using behave for cli testing, but the test code is not that readable due to the required overhead... it seems like i implemented some parts of behave4cmd0. Is the uncommented code in behave/behave4cmd0/command_util.py, failing_steps.py, pathutil.py and textutil.py untested code?

[jenisys]

With "uncommented code" you probably mean the "code that is commented out".

In "command_util.py" that are functions that were moved to another module (refactoring).
In "failing_steps.py" that is just another step that should not be used any more.
Same for "pathutil.py" (as far as I see it).

[fkromer]

You are right, sorry for my english. Thanks.

[lampmantech]

I too really look forward to behave4cmd0 being broken out to it's own package - the one included with behave is great, and it should be its own package.

If you break it out, maybe call it behave4clirather than behave4cmd just to avoid confusion with the behaving.cmd step library, which is a lightweight step library for files and commands.: https://github.com/lampmantech/behaving.cmd

behave4cmd0 is much more than just a step library so I doubt it should be structured as behaving.cli but you might want to look at it - I haven't thought about that. But I feel it's important to get the structures right so that the step libraries can work together. It's something that RobotFramework did well, and behave has been lacking so far.

[jenisys]

@lampmantech
Sorry, I came up with the name behave4cmd first (as I see it). Therefore, there is currently no name change planned. But I will have a look at your project.

And I agree with you. Behave (and the other cucumber implementations) need step-libraries for the specific problem domains. There are some, but I have only seen a few that are publicly available.

[jenisys]

@lampmantech
Hey, you are using step aliases by using the step-decorators multiple times (in behaving.cmd). I haven't even thought about that doing it like that 😄.