Skip to content

Add Automated Tests #3

@princefishthrower

Description

@princefishthrower

Other than doing some smoke tests via the interactive demo site, I have no other testing method currently for the code in this repo 😅

I'm partial to end-to-end testing tools for a project like this (like cypress for example) because our tests can truly observe the changes in document.title and the <link rel="..."> values.

I'm looking for the following:

  • End to end test to be written in a tool like Cypress (doesn't have to be Cypress, if you can convince me otherwise)
    • Cycle through all possible option configurations with multiple values
    • Keep tests small so it is easy to see exactly which test is testing what
  • I'm also open to unit tests, though less experienced with them. It's also debatable if a repository this size needs them. Then again, perhaps we need them exactly because of the simplicity of the codebase - small changes can potentially break the whole hook.

This PR could potentially expand into multiple PRs - setting up tests first locally, then adding it to a CI / CD process (which also doesn't exist yet 😅 ) etc. etc.

Metadata

Metadata

Labels

hacktoberfestIssue designated for Hacktoberfest

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions