Add e2e tests: Treat examples like a fixture? about autodll-webpack-plugin

[viankakrisna]

To avoid issue like #21

[asfktz]

I'm not familiar with fixtures, but it sounds exactly like what I was looking for.

Can you please tell me more about it?

[viankakrisna]

Taken from here

A test fixture is a fixed state of a set of objects used as a baseline for running tests. The purpose of a test fixture is to ensure that there is a well known and fixed environment in which tests are run so that results are repeatable.

[viankakrisna]

I'm new to this testing world (haven't yet set it up from scratch), so I hope I don't use the wrong term here 😄

Basically, it's a file/set of file that we run our test for, to test multiple real world scenario.

[asfktz]

Looks like something I need to dive into 😄
Will do.

[viankakrisna]

I think this looks more like an e2e test, I don't know if we should use examples as fixtures or written it separately. The test looks like this https://github.com/viankakrisna/autodll-webpack-plugin/blob/1d5979f96a556764fd862410110814beb2e7643f/specs/features.spec.js

[viankakrisna]

Possible e2e cases to be added:

Integration with other webpack plugins:

• SWPrecache
• ManifestPlugin
• ExtractTextPlugin

This is what commonly used plugins, at least, it used in CRA. If we can write tests and manage compatibility with it, surely it would boost the confidence level to be used in it :)

[asfktz]

I started to work on it.
This article looks interesting: https://blog.iansinnott.com/testing-webpack-plugins/

[viankakrisna]

Great! thanks for sharing it 👍

[asfktz]

Of Course (:

[asfktz]

Done! Thanks for convincing me to add it @viankakrisna, it turns out to be very useful.