About testing

[hyf0]

Discussion for testing in RSpack

@bvanjoi @IWANABETHATGUY @wre232114 @iheyunfei

[hyf0]

To be specific, we should have the same test ability as webpack.
I have already implemented the CSS version in https://github.com/speedy-js/rspack/tree/next/crates/rspack_plugin_css.

I think it's better than snapshots testing

• We could also test the filename
• multiple files

But I'm open to snapshots testing if it could do the same ability.

We also need to have the same macro like swc to enable concurrency in tests.

[liuliudada-w]

In my opinion, the test function have two parts.

• Each independent function module functional module such as CSS，Assets、HTML and more should have the same test abilities as webpack( In my view this is the snapshot test )
• For each functional function, we also need unit tests. There are two main issues to discuss in this part. First, whether to force each function to have a corresponding unit test? Second, how should we control unit tests, is it written in the corresponding file or managed at the top level?

[hardfist]

we may need something like load-runner to test load behavior out of rspack implementation like webpack https://github.com/webpack/loader-runner

[hyf0]

Conclustions

• Need the same test ability as webpack
  • Split the test ability into a single crate to reuse. The same test ability as webpack #436
  • Update snapshot automatically
  • Concurrency test macros Testing macros #431
• No unit tests for now
• No loader-runner abstraction for now