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

Adds verification of TagNode.location_path to the integration tests #87

Open
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

funkyfuture
Copy link
Contributor

this is the questionable approach that i mentioned earlier. i think it's justified well enough.

@funkyfuture funkyfuture added this to the 0.5 milestone May 11, 2024
.editorconfig Outdated Show resolved Hide resolved
@JKatzwinkel
Copy link
Contributor

lmao Screenshot from 2024-05-11 17-29-09

from typing import Final

# Neukölln's digest
PROGRESS_INDICATION_CHARCATERS: Final = "✓→🚴✊★☆⯪𓄁𓅯▶️✴️🪇⚒️🧻🚬🗿🎳⏳🌝☕🐑🐞🌼🪱🌸🏵💮️"
Copy link
Contributor

Choose a reason for hiding this comment

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

the i think fairly standard font i use for code doesn't have a lot of those charcaters...

@funkyfuture
Copy link
Contributor Author

lmao Screenshot from 2024-05-11 17-29-09

it's beautiful and actually that makes up for my lack of representing the prevalence of geometric forms on Neukölln bodies.

funkyfuture and others added 5 commits May 12, 2024 14:31
includes minor cosmetics applied to scripts.
With each run a randomly selected sample of data from the corpora is
tested.
The inclusion as integration test is motivated by the fact that a
representative coverage in the unit tests would take too much time.
At the same time, there are no relevant criteria to curate a subset
of documents for testing and such curation would have to be repeated
for future extensions of the corpora.

A future interface for running these tests could include
configuration options to set the sample sizes.
@funkyfuture funkyfuture force-pushed the integration-tests-location-path branch from 4f1026c to 2239b76 Compare May 12, 2024 12:56
@funkyfuture
Copy link
Contributor Author

ACHTUNG! i force-pushed.

i'd say we stick with not using hatch as an entrypoint for these tasks. for now textual information on how to deal with these should not be too complex.

JKatzwinkel
JKatzwinkel previously approved these changes May 12, 2024
@JKatzwinkel
Copy link
Contributor

gonna be afk for a few days

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.

None yet

2 participants