VAGOV-5767: Add WEB tests to CMS test suite.

[jonpugh]

This PR adds the new test va/web/unit.

It kicks off the WEB unit tests after the WEB build and Behat tests run.

this PR is only going to add this test. Getting the full WEB test suite to pass requires further work.

Background

Environment variables and CLI options affect the build:
NODE_ENV=prod
--buildtype=VAGOVPROD will cause the build to fail if there are bad links.

So... Do we want the build to fail if the link checker fails? because right now that would block a merge! Who would this be a question for, @swirtSJW ?

[jonpugh]

First run for me results in a looping "Connection refused", presumably from the Mock API server.

[swirtSJW]

@jonpugh That is an interesting find. Generally I am opposed to hamstringing development by content which is unrelated to development. If there were a way to check whether the links were failing because of code, that would be one thing, but making all development PR's fail because an editor enters a bad link or menu entry is making a dependency that should not exist.

[jonpugh]

Making all development PR's fail because an editor enters a bad link or menu entry is making a dependency that should not exist.

Oh, totally! That link checker fires about 100% of the time in my experience, so, we'll have to find a happy medium.

From my conversations with @ncksllvn, I think the other part that this change affects is the accessibility tests: With this new flag an a11y test fail will fail the build.

[jonpugh]

I'm not planning on spending much more time on this today.

I think I will roll back this PR to just get va/web/tests/unit passing

[swirtSJW]

Reviewed but have not tested yet. If this does not fail our build based on FE tests of links and accessibility, I am good with it.

[ElijahLynn]

I changed the base branch from develop to master as we switched our CD to be based on the GitHub Flow model (as opposed to Git Flow) and develop is now deprecated (#617). It may be best instead of fixing conflicts to rebase/replay your commits on top of current master:

git fetch --all
git rebase origin/master
git push --force

[jonpugh]

I want to bring this back once we have the Rebuild Web uI.

[swirtSJW]

Blowing the dust off this. @jonpugh Does this do something we aren't already doing or can we close it?

[swirtSJW]

Closing this as unresponsive. Re-open if needed.