-
Notifications
You must be signed in to change notification settings - Fork 3
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
[Question] Unit tests ? #3
Comments
I agree with you but I am also not sure how to start mainly because of the "maintaining URI" part. You can just submit PR and modify codes however you want, seems like I'm the only one who is using this library seriously 😂 |
By the way, even the official DocumentFile library is not properly tested 🤷 this is all they're doing |
OK. I think I found a way The combination of MANAGE_EXTERNAL_STORAGE flag and android emulator github action should do the trick 🎉 |
...and we know what it lead to 😆 Seriously, Google have done many outstanding things, but goddamn SAF is definitely not one of them 🤦 |
Well, I'm gonna do that PR anyway because the piece of code you got from avluis doesn't work on Android 11 (we just found out about that last week) However, I still haven't abandoned the idea of externalizing file I/O to a library such as that one. It makes sense to join our forces to simplify that part of Android. Please let me know when you have the first unit test running, I'll take some time to increase coverage 😉 |
okay, I think I found a way |
I pushed the code to dev branch that grants permission automatically. You can run the tests locally by running tests in |
As far as i'm concerned, API21 is fine. I'll take a look and get back to you soon. |
@tom5079 Sorry for the delay, I've been focused on my roadmap for quite a while. Just tested your new unit test successfuly. What you've done to enable permissions is devilish... but hey, it works, so no complaints here ! 😉 I'll post some newer tests soon. Thanks for the hard work ! |
No problem, and thanks for your interest! |
I'd like to contribute a few additions but, as there's no documentation and no design documents, I'm kinda afraid to break things without realizing it.
I guess you're testing new changes through your app, which is totally fine as far as you're concerned, but imo not enough for a library aimed at being reusable outside of that app.
=> Is there a way we could set up unit tests to detect any regression and somehow show how the API works ?
I'm not sure how to start, but I would definitely help enrich the first tests if you got a few of them running...
The text was updated successfully, but these errors were encountered: