Review test structure

[anatoly-scherbakov]

We need to discuss testing structure. Function-based tests, fine, but I don't want to end up with hundreds of AI generated tests that we can no longer navigate. And the very least we should stick to one file per function

Originally posted by @mielvds in #249 (review)

[anatoly-scherbakov]

I agree. I like smaller files more than bigger ones. @mielvds we could record these requirements in AGENTS.md.

[mielvds]

Ideally, I'd like the tests file structure to mimic the code file structure, as is common. This is currently the case, but we probably need to split up jsonld.py more first before we can get something maintainable.

How would you partition these function-based tests, @anatoly-scherbakov ?

• One file per "problem" (e.g. regression tests)
• one file per python function
• one file per lib/*/*.py file?