[testing] module first approach

[LarsDenBakker]

Currently our testing package relies on modifying globals. This makes tests non self contained and requires some magic to happen before test files are run, either in a parent index.html / index.js and/or requires test tool configuration.

My proposal is to go fully with modules, in your tests use: import chai from '@open-wc/testing which contains all the necessary plugins registered. The same goes for the automatic fixture cleanup, we could register this automatically when you create a fixture or also when you import chai.

[daKmoR]

so to not be dependent on webpack as a build tool... this means we should use a "native" es module version of chai.

So basically add it to https://github.com/bundled-es-modules right? and then use that one instead of the "official" chai

[LarsDenBakker]

Yes if we want to stick to native es modules for everything we will need to do that. Alternatively we could check if express can be loaded with an import, and export from the window.

[daKmoR]

I would say the more "correct" solution would be "native" es modules for chai itself. using it via some express magic feels like a workaround.

We should do this for sinon then as well 💪

PS: just thinking using renovate auto merge + fully CD we should be able to get automatically new versions released (without any manual work)... uh that sounds like a good plan for bundled-es-modules

[LarsDenBakker]

Sinon 7 ships native es modules :D wct is still on sinon v1 haha.

Are you able to make the es version of chai? Then ill work on the changes to the testing package

[daKmoR]

uuhh nice - native es version 👍

sounds good will make it right now :) published name will be @bundled-es-modules/chai I guess

[daKmoR]

solved with latest release