Skip to content

Conversation

@colinjlacy
Copy link
Contributor

@colinjlacy colinjlacy commented Nov 23, 2025

This branch adds unit tests in the integration
style to the internal/libyaml directory. it
focuses primarily on the majority use cases and
does not get too creative with edge-case yaml
examples, which can likely be filled in as issues
are opened and bugs are squashed. The majority of
these tests were written by Claude in cursor.

To test, simply run:

make test-all
go test ./... --cover

fixes #149 in part

@ingydotnet
Copy link
Member

go test ./... --cover

Can you add test-cover rule to the Makefile for that?

@colinjlacy colinjlacy force-pushed the issue149_add-internal-tests branch from f5c7eac to f9ecb9f Compare December 3, 2025 10:14
Copy link
Contributor

@ccoVeille ccoVeille left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't review all tests. But based in the fact you are not updating the code, but adding tests I feel like I can approve anyway.

@ingydotnet ingydotnet force-pushed the issue149_add-internal-tests branch from 849f684 to e968d03 Compare December 4, 2025 14:06
ingydotnet added a commit that referenced this pull request Dec 5, 2025
Refactored from @colinjlacy's #184

Use super clean, simple, consistent and documented foo_test.yaml files
for test data, and minimal foo_test.go files for the code running the
tests.
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

Successfully merging this pull request may close these issues.

Do we need tests for the internal and cmd dirs?

3 participants