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

Separate valid GEDCOM 5.5.1 from invalid GEDCOM 5.5.1 into separate test files #8

Open
dthaler opened this issue Mar 22, 2022 · 0 comments

Comments

@dthaler
Copy link
Contributor

dthaler commented Mar 22, 2022

Currently date-all.ged and date-dual.ged contain both valid and invalid GEDCOM 5.5.1.
I would request that they be separated so that the valid ones can be used for validation/compliance/etc tests that would apply to most programs since the tests would implement recommended practices such as in the migration guide,
whereas the behavior of handling invalid GEDCOM 5.5.1 can legitimately vary by implementation and so other implementations would not be expected to match the GEDCOM 7 output.

@dthaler dthaler changed the title Separate valid GEDCOM 5.5.1 from invalid GEDCOM 5.5.1 into separate tests Separate valid GEDCOM 5.5.1 from invalid GEDCOM 5.5.1 into separate test files Mar 22, 2022
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