p5.js-web-editor
p5.js-web-editor copied to clipboard
Added tests for user/pages folder
Fixes #2923
Changes:
I have verified that this pull request:
- [x] has no linting errors (
npm run lint) - [x] has no test errors (
npm run test) - [x] is from a uniquely-named feature branch and is up to date with the
developbranch. - [x] is descriptively named and links to an issue number, i.e.
Fixes #123
🎉 Thanks for opening this pull request! Please check out our contributing guidelines if you haven't already.
This looks to be a nice start. I think there needs to be more discussion on the testing strategy and what the goals are. Addressing questions like:
- What kind of unit tests will increase your confidence that the component is functional? testing existence of elements and its count is nice, are there any kind of tests depending on the component that might help with testing?
- Using data id locators is great, noticed you have used it in some places. When should is it preferable over role/label text locators?
And other questions would help guide the implementation better. (Not a maintainer, just my thoughts). any feedback @raclim ?