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

Build automated QA checks #598

Open
stucka opened this issue Jan 5, 2024 · 1 comment
Open

Build automated QA checks #598

stucka opened this issue Jan 5, 2024 · 1 comment

Comments

@stucka
Copy link
Contributor

stucka commented Jan 5, 2024

As @Kirkman found in #597 , a scraper can stop producing output without triggering an error in workflow.

While a few states keep WARN and non-WARN layoffs in the same database it's unlikely that many states would ever have a reduction in the number of incidents reported in the files getting scraped. So if a state moves from 283 reports to 123 reports or 0 reports that should get flagged. Simple row counts of CSVs compared to earlier snapshots would have caught Missouri problem.

Weekly Github Action built in warn-support repo, perhaps?

@chriszs
Copy link
Contributor

chriszs commented Mar 10, 2024

Looks like how to approach this problem is being considered over in biglocalnews/warn-transformer#236

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

No branches or pull requests

2 participants