test(nodeOps): rename file, fix type errors, add tests

[andretchen0]

Problem

src/core/nodeOps.ts has a test file, but it's called nodeOpts.test.ts – note the extra 't'.

Solution

Rename to src/core/nodeOps.test.ts.

Problem

The test file had a lot of type errors.

Solution

Fix most type errors.

Problem

The test file was organized in a flat hierarchy, leading to a lot of repetition of names createElement should ....

Solution

Group tests using describe

Problem

There's no way to easily see test coverage.

Solution

Add test coverage plugin to Vitest and add to pnpm run test:ui script.

Here's how to use it in the UI.

Problem

nodeOps test coverage is about 50%, which makes changes riskier than they could be.

Solution

Improve test coverage

---

closes #631

[netlify]

✅ Deploy Preview for tresjs-docs ready!

Name	Link
🔨 Latest commit	6fd8c08
🔍 Latest deploy log	https://app.netlify.com/sites/tresjs-docs/deploys/661a3571d613c40008640ab5
😎 Deploy Preview	https://deploy-preview-637--tresjs-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[andretchen0]

Hey @alvarosabu !

I increased test coverage of nodeOps to about 90%.

• Could you have a look and see if anything stands out: Do the tests reflect the intention of the code?
• I'm not sure what to do about things like deregisterAtPointerEventHandlerIfRequired. It was said that these were going away, so I didn't write tests. Is that right?
• There are still gaps, but fewer and smaller. Feel free to suggest more tests.

[alvarosabu]

Hi @andretchen0 thanks a lot for submitting this PR, I'm so happy to have proper coverage, especially on the nodeOps. This will make our maintenance easier.

I'm not sure what to do about things like deregisterAtPointerEventHandlerIfRequired. It was said that these were going away, so I didn't write tests. Is that right?

Yes, that is going to disappear (check #515)

You would need to change the origin to v4 instead of main since you branch from v4. There are a lot of changes in this PR that don't belong.

[andretchen0]

@alvarosabu

v4

Whoops! Thanks for the heads up! Fixed.