Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add proper testing #8

Closed
2 tasks
XVilka opened this issue Jan 19, 2021 · 10 comments · Fixed by #15
Closed
2 tasks

Add proper testing #8

XVilka opened this issue Jan 19, 2021 · 10 comments · Fixed by #15

Comments

@XVilka
Copy link
Member

XVilka commented Jan 19, 2021

  • pytest for Python
  • etc
@4thel00z
Copy link
Contributor

4thel00z commented Mar 5, 2021

Hi @XVilka can give me some details what is needed here? I would like to contribute that

@XVilka
Copy link
Member Author

XVilka commented Mar 6, 2021

@4thel00z for example, implement a set of tests for rz-pipe.py with pytest framework.

@4thel00z
Copy link
Contributor

4thel00z commented Mar 6, 2021

ok, I can do that

@4thel00z
Copy link
Contributor

4thel00z commented Mar 6, 2021

I will refactor it too, it is really not easy to follow along

@4thel00z
Copy link
Contributor

@XVilka what can you tell me about RZ_PIPE_IN, RZ_PIPE_OUT / RZ_PIPE_PATH? What is the path where rizin usually creates these

@wargio
Copy link
Member

wargio commented Mar 14, 2021

they are environment variables. i think the varnames are RZPIPE_*. there is no default path. actually they need to be defined

@wargio
Copy link
Member

wargio commented Mar 14, 2021

rzpipe_path is the path to a unix file pipe

@wargio wargio linked a pull request Mar 15, 2021 that will close this issue
@4thel00z
Copy link
Contributor

4thel00z commented Mar 16, 2021

@wargio @XVilka @officialcjunior
How does one join the rizinorg btw, I will try to contribute semi-regularly as I am interested in the project

@wargio
I see that these are env vars from the rzpipe code, but I need to know to what these need to point to, so I can mock them in the test
I will just try to read through some rizin code to understand what's happening

@thestr4ng3r
Copy link
Member

On unix systems, _IN and _OUT are simply file descriptors that the parent process (rizin) creates and child (rz-pipe) can read/write from/to:
https://github.com/rizinorg/rizin/blob/a4b2a942c9a398a1d6f0c62b2c60cdcecfc0bd49/librz/lang/p/pipe.c#L159-L160

On Windows it's a bit different, there it uses a named pipe and the _PATH var:
https://github.com/rizinorg/rizin/blob/a4b2a942c9a398a1d6f0c62b2c60cdcecfc0bd49/librz/lang/p/pipe.c#L238-L242

@ITAYC0HEN
Copy link
Member

@4thel00z

How does one join the rizinorg btw, I will try to contribute semi-regularly as I am interested in the project

We will be more than happy to have you in Rizin :) You can jump into our Mattermost server and check out the different channels, including Rizin dev: https://im.rizin.re/
Other platforms available here: https://rizin.re/community/

See you in there! :)

@wargio wargio closed this as completed in #15 Jun 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants