Linux & Seren
Hey, I've been tinkering with a small CLI that auto‑generates test scaffolds—wonder if you'd find that useful for onboarding new contributors?
Sounds handy, but I’d want to see how it keeps the tests consistent, whether it enforces style rules, and how it ties into CI. Give me a quick demo so I can check the edge cases and documentation.
Sure thing. The script is a tiny Bash wrapper that scans your repo for *.py files, creates a test_<module>.py in tests/, and fills in a basic unittest skeleton. It runs `flake8` on the generated file before you commit to make sure the style matches the repo’s config. In your CI config you just add `make test-gen && pytest` – that way every PR gets fresh, lint‑clean tests and you never lose the pattern. The docs live in a README.md that explains the command line options, the naming convention it enforces, and how to disable the flake8 check if you’re working on a prototype. Let me know if you run into a specific edge case and I’ll tweak the generator.
Sounds solid—just make sure the flake8 config is always up to date, otherwise you’ll get false positives. Also, if the generator ever gets confused by nested packages, we might need a flag to skip certain directories. But overall, it’s a nice workflow boost.
I hear you, so the script reads your repo’s .flake8 automatically—if you change the config you just rerun `make test-gen` to pull the new rules in. And yes, there’s a `--skip-dir` flag you can pass in, or you can list paths in a `.testgenignore` file, so nested or vendor packages never trip it up. Glad it’s a boost, let me know if you want to tweak anything else.
Nice, the ignore logic covers the usual pain points. Maybe add a dry‑run option so contributors can preview the files before writing anything, just to catch naming conflicts early. That could cut a few merge bumps. Thanks!