Run each set of tests in separate iframe

This would make karma also superb for integration (and such) tests. As they can easily pollute global variables or fixtures.

This would be awesome to have files variable in config file to accept something like:

files = [
    ['file.js', 'file.spec.js'],
    ['lib.js', 'lib.spec.js']
]

or an object

files = {
    'fileTest': ['file.js', 'file.spec.js'],
    'libTest': ['lib.js', 'lib.spec.js']
}

so you could name each set

and each array would be set of files to be loaded in a separate iframe so you would not have to worry about polluting environment and just focus on integration tests itself

[bashmish]

This might be really helpful when testing custom elements (web components). For now there is only one single registry and no way to unregister an element. Though there is this idea to have scoped registries which does not have a concrete proposal yet.

This old discussion about the possibility to unregister didn’t go further than pointing out that there are test frameworks which already run tests in iframes, which is the web-component-tester. But web-component-tester is also very limited and only allows running individual suites in iframes, not individual tests. I created a repo to show this behavior. Looks like the above mentioned karma-iframes is similar to the WCT behavior.

I can understand that this use case is not trivial. But maybe it is time to reconsider and reopen the issue at least to explore possible use-cases further.

[lancedikson]

I’m currently having the same situation with custom elements (Web Components) testing and struggling with setting up integration and unit tests, where each component can be registered only once and there’s no way to unregister it. It produces very specific workarounds after all. Let’s try to call active maintainers to re-check this issue and maybe re-open it because the problem is getting more and more common due to the growing popularity of WebComponents. @johnjbarton 🙏