-
Notifications
You must be signed in to change notification settings - Fork 16
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
Unit tests for issue #90 #137
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: HanslettTheDev <HanslettTheDev@gmail.com>
…rom rb to r and write more from wb to w Signed-off-by: HanslettTheDev <HanslettTheDev@gmail.com>
…ning tests Signed-off-by: HanslettTheDev <HanslettTheDev@gmail.com>
Signed-off-by: HanslettTheDev <HanslettTheDev@gmail.com>
Signed-off-by: HanslettTheDev <HanslettTheDev@gmail.com>
Signed-off-by: HanslettTheDev <HanslettTheDev@gmail.com>
Signed-off-by: HanslettTheDev <HanslettTheDev@gmail.com>
Signed-off-by: HanslettTheDev <HanslettTheDev@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR seems like a nice initial attempt for coverage of this file formats unit tests.
It would be great to have more real tests for TXT and DBF file formats, specially with a real invoice fields and values.
Most of the UT here are pretty simple, and sample files entrada.txt and facturas.json don't seems to be used.
A similar sample file for DBF would be great.
And you should check field and formats like in the CSV file format unit tests.
If you want we can merge this PR and create the more extensive UT in a new PR
Summary
This PR aims to close issue #90. The PR contains unit tests for the following files in formatos module
Checklist
Manual test evidence
(attach command-line examples, execution output & logs, etc.)