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

oUnit in a non-command-line environment #51

Open
gildor478 opened this issue Oct 24, 2020 · 0 comments
Open

oUnit in a non-command-line environment #51

gildor478 opened this issue Oct 24, 2020 · 0 comments

Comments

@gildor478
Copy link
Owner

This feature request has been migrated from artifact #1454 on forge.ocamlcore.org. It was assigned to user100.

user7322 posted on 2015-02-18 13:55:44:

Hi,

we'd like to use oUnit in an environment where you cannot start commands on your own (in our case this is an iOS app). This means that there is no way to set Sys.argv, and the ocaml code will be invoked from an Objective-C wrapper. There is also no stdout/stderr (but I guess I can redirect this to a temp file).

So, we'd like to pass at least argv to run_test_tt_main. I don't know what else needs to be done to reconfigure oUnit for this target. IOS is a quite constrained environment, and in particular access to files is restricted.

I have some time to help, but I'd like to know whether such an extension would be welcome.

Gerd

user102 replied on 2015-02-18 14:44:39:

I think that is totally doable and your contribution will be more than welcome. Have a look at the source code and tell me precisely the change you want to make (Sys.argv can be a start, I suppose you have to create a specific oUnitLogger as well).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant