Develop a scraper automating testing strategy/guidelines
Open
Nobody has claimed this yet.
question
- Dominant language
- HTML
- Stars
- 9
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Scrapers suffer regularly of regressions which take roots in:
- Coding errors
- Changing upstream
We have no clear strategy so far to reduce the number and impact of the regressions.
This issue is there to discuss how we could do better by raising standard approaches.
This issue is a follow-up of #43
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing follow-up issue #43 and the regression causes identified here: coding errors and upstream changes. Establish and document a testing strategy and guidelines for scrapers, with clear approaches for reducing regression frequency and impact; completion should be an agreed set of standard practices.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, testing-qa
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100