Web Design Task Assessor and Pytest testing question

I’m currently working on a project for assessing web pages and web sites, but I would like some advice on packaging the project (in particular setting up the folder structure, tests, and dependencies).

I’m building out a project that will assess the semantics, elements, and syntax of Web Design tasks. It will inspect and run tests on HTML and CSS (I’ll probably add JS once everything else is in place).

I’m wanting to develop a series of web design tasks (pretest, single web page, image gallery, 2-column layout, mobile-first layout, and posttest).

Each task will…

  • use the same basic module for the Validator API calls and document parsing.
  • use a base set of unit tests (for every task, like does it pass the validator)
  • contain tests unique to the task at hand (like inspecting the @media queries for mobile first stylesheet, or specific tags used for the image gallery or layouts, etc.)

I currently have some proof of concept Python code that is able to:

  • send an HTML file to the W3C Validator API and receive a JSON object of error messages
  • Parse an HTML File by returning an array of opening tags, content, and ending tags in their order of appearance

I’m currently developing it as a Python project (in order to leverage Python’s many files for API calls and unit testing).

So here are my questions:

  • should I develop one base project and the fork it for each task?
  • should I bundle it all as one project with multiple folders: one for each task?
  • If I bundle it all as one project, how should I package the tests so that they all rely on one base module and standard tests for every task and then include specialized tests?

I’m leaning towards the last option mainly because if I fork projects and then discover a bug in the base module (i.e. dependencies), then it becomes more work to push out the hotfix.

Thoughts? Suggestions?

Since posting this, I think I’ve been thinking about it all wrong. I think the way to go about this is to focus on the testing suite and develop it.

Like I said, I already have some proof of concept work. I can begin developing that into a pytest library.

I still welcome suggestions and ideas.

PS - I believe my posts are proof that rubber ducky debugging works.

Hey all.

I’m trying to choose a name for my project that is more succint, and I have two main ideas, but I’m open to other suggestions.

My top two choices are between webanalyst and webvestigator

  • Any thoughts on my two ideas?
  • Any other name suggestions?

If you have another name suggestion, you might want to google it to make sure it hasn’t already been taken.

© 2017 GitHub, Inc.
with by
GitHub Education