Introduce yarn run test:full

[florian-richter]

Proposed Changes

There is a small number of very slow tests. This makes it annoying to run yarn test locally. Now I introduced yarn run test:full and excluded the slow tests when using yarn test.

Checklist

• I have added or adjusted tests that prove my fix is effective or that my feature works

[mr-flannery]

I think generally an approach like this is fine, but I'm afraid that we're opening Pandora's box here, speaking from a cultural perspective. So I do want to raise the questions: why are these tests slow? And is there something we can do about it?

[florian-richter]

They are not actually unit tests, but end-to-end tests since they are installing dependencies via npm or creating a new project via the nest cli (through npx).

Since they are fairly contained from the code that is being checked, I somewhat like that they are in the same file as related unit tests. I guess it isn't a best practice to mix different levels of tests like this, but the alternatives seem worse in our specific case (splitting the files, using different test frameworks, ...)

[mr-flannery]

It's fine for me for now. I think it would be good to get feedback from at least one other person (@marikaner @FrankEssenberger @jjtang1985).

[marikaner]

I agree with @mr-flannery here, but I see that this is probably the most pragmatic solution. Still, I am not a fan of the framing of "SLOW" tests as it has a negative connotation in terms of tests. Consider whether "E2E" or "INTEGRATION" are better names.