Updating webpack-cli and webpack-dev-server. Adding projects test to CI

[berhalak]

Context

• webpack-cli package was outdated, which caused webpack-dev-server to fail.
• projects tests are now added to CI

Related issues

#1811

Has this been tested?

Existing test should pass.

[paulfitz]

@berhalak what do you think about the test failure?

[paulfitz]

@berhalak I think I can replicate the failure locally with something like:

MOCHA_WEBDRIVER_SKIP_CLEANUP=1 MOCHA_WEBDRIVER_HEADLESS=1 yarn run test:projects -g "contextMenu"

I think removing MOCHA_WEBDRIVER_SKIP_CLEANUP: 1 from projects run would be the simplest solution. It is there for when mocha is run in parallel mode.

[berhalak]

@berhalak I think I can replicate the failure locally with something like:

MOCHA_WEBDRIVER_SKIP_CLEANUP=1 MOCHA_WEBDRIVER_HEADLESS=1 yarn run test:projects -g "contextMenu"

I think removing MOCHA_WEBDRIVER_SKIP_CLEANUP: 1 from projects run would be the simplest solution. It is there for when mocha is run in parallel mode.

Thanks for finding this out @paulfitz! I'm still not happy that this doesn't work for projects (while it does work for nbrowser tests), but couldn't find the reason, and I think this is good as it is.

[dsagal]

Jumping in while Paul is out. This looks good, and thank you for fixing all those tests! I have a couple minor comments, non-blocking.

[dsagal]

Is this needed? (I always have to adjust when I run such tests locally because bigScreen is bigger than my physical screen)

[berhalak]

It is. It will fail with the full browser without it. But the size of the window can be adjusted globally (Cyprian already raised that issue before), I will propose a change as a DIFF as more test will be affected.

[dsagal]

We do have gu.bigScreen('medium'), and to me that would be a more convenient default. Totally fine to leave as is in this PR.

[dsagal]

Might it be better to keep in "ColorSelect", since it's rather specific to the needs of that test? If you'd rather expose it here for other purposes, then I think it needs a clearer name, since "selection" is used for several different things in our tests (like cell ranges, or selected menu items). Maybe "waitForInputFullSelection"? It could also accept a WebElement, for better generality (you can pass one to executeScript, e.g. as for scrollIntoView)