Draft
Conversation
- Add tests subdirectory to build system (configure.ac, Makefile.am) - Create modular test structure with subdirectories: * fixed_length: Fixed-length parsing with XML output * separated: CSV parsing with identical XML output * binary: Binary data parsing with hex dump * expressions: Record filtering with -e option - Master runner script (run_tests.sh) executes all tests - All tests pass with make check - Test files organized by functionality for maintainability 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft PR.
Again, not necessarily something necessary, especially because ffe doesn't get updated often anymore. But I did this as a holiday project to learn a few additional skills.
This adds unit tests and CI workflows to build the project for different platforms and release it as a Github release.
The tests do an end-to-end test using the compiled executable, taking an input file, .fferc configuration file and expected output file. It uses the bats-core test framework, which is "a TAP-compliant testing framework for Bash."
Disclaimer: I used agentic coding heavily to generate the test cases, using the current ffe documetation as the input spec. I think it worked out well, but I can't claim that I've covered every single edge case. The tests also serve as a useful corpus of examples.
Even though this is still a draft, if you have the time, I'd love some feedback. No rush, of course.