goodreasonai / goodreasonai/ScrapeServ

Need testing framework

Open
#15 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
1.2k
Forks
82
PR merge metrics
No merged PRs in 30d

Description

Good code has test, and this repo has little testing. I (someone?) should add a comprehensive testing framework. There are some complications here related to the fact that you might want to test against third party websites that change. A good approach might be a (1) pytests that call the API like a client and (2) a webserver that serves a bunch of different content - PDFs, other kinds of files, weird mimetypes, complicated javascript, resource intensive pages, etc. So the tests would ping the scraper, which in turn would scrape localhost:5678, say, which would be our testing playground.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the proposed pytest API-client approach and the localhost:5678 testing playground described in the issue. Define repeatable coverage for PDFs, other files, unusual MIME types, complicated JavaScript, and resource-intensive pages; done means the scraper is exercised against these cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.