You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 21, 2021. It is now read-only.
With v0.1.0 being prepped for release soon as a big change to a lot of the library's API, and general additions. I want v0.1.1 to focus on complete-ness, instead of big changes. Which the first step would be working on unit testing, to make sure future changes and functionality in general is robust.
Not having done much of JS unit testing, I need to start looking into different frameworks, best practices, etc. I've projects such as Jest or Mocha, which seems to be a common gotos. But it doesn't seem to provide a Browser context? Which is needed for testing Browser-exclusive functionality.
Which for that, Cypress seems to be the go to, in the Svelte community anyway. Being used for the official Sapper Starter Template.
I also want to start looking into GitHub Action afterwards, to have testing on commit and releases.
The text was updated successfully, but these errors were encountered:
Description
With v0.1.0 being prepped for release soon as a big change to a lot of the library's API, and general additions. I want v0.1.1 to focus on complete-ness, instead of big changes. Which the first step would be working on unit testing, to make sure future changes and functionality in general is robust.
Not having done much of JS unit testing, I need to start looking into different frameworks, best practices, etc. I've projects such as Jest or Mocha, which seems to be a common gotos. But it doesn't seem to provide a Browser context? Which is needed for testing Browser-exclusive functionality.
Which for that, Cypress seems to be the go to, in the Svelte community anyway. Being used for the official Sapper Starter Template.
I also want to start looking into GitHub Action afterwards, to have testing on commit and releases.
The text was updated successfully, but these errors were encountered: