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 test suite #2

Open
morgant opened this issue Feb 3, 2019 · 4 comments
Open

Add test suite #2

morgant opened this issue Feb 3, 2019 · 4 comments
Assignees

Comments

@morgant
Copy link
Owner

morgant commented Feb 3, 2019

I tested this when I wrote it, but—esp. since it’s relying on several third party tools—it really needs some functional tests to be implemented to try to catch any edge cases.

@morgant
Copy link
Owner Author

morgant commented Feb 3, 2019

I have used & liked Blake Mizerany’s roundup for testing shell scripts, plus have used it with TravisCI (see realpath‘s .travis.yml).

@morgant
Copy link
Owner Author

morgant commented Feb 3, 2019

In investigating today, I believe the best way to implement tests is to use Rez/DeRez to create & verify the resource fork data before & after any conversions (probably just a 'STR ' resource, or something). I'm having some difficulty digging up good documentation on the format, of course. I'll dig some more.

@morgant
Copy link
Owner Author

morgant commented Feb 6, 2019

I was able to find enough information in the Rez manual and Inside Macintosh: More Macintosh Toolbox to piece together a Rez command to build a file with a resource fork. I've added a test for whether forks are split upon commit using that method.

@morgant morgant self-assigned this Feb 6, 2019
@morgant
Copy link
Owner Author

morgant commented Feb 9, 2019

I've added test suites for Rez, SplitForks, and FixupResourceForks to confirm they work as expected/documented, plus to confirm my methodology for testing resource forks & AppleDouble files. You can find them and my progress on tests for the hooks in my roundup_tests branch.

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

No branches or pull requests

1 participant