Update mocha, chai for testomat reporting internal

[achakko]

Description:

This is a pull request to update mocha, chai version for all tests, thereby to help enable CI integration with testomat.io to understand reporting on tests including flakiness

Review

• Functional review done
• Potential edge cases thought about (behavior of the code with strange input, with strange internal state or possible interactions with other Matomo subsystems)
• Usability review done (is anything maybe unclear or think about anything that would cause people to reach out to support)
• Security review done
• Wording review done
• Code review done
• Tests were added if useful/possible
• Reviewed for breaking changes
• Developer changelog updated if needed
• Documentation added if needed
• Existing documentation updated if needed

[sgiehl]

Seems you have commited a couple changes to the submodules. This for sure shouldn't be included in this PR and currently causes a lot tests to fail.
You may need to revert those changes. If you need help with git or how to handle submodules feel free to get in touch with me or another dev on slack

[achakko]

Hi @sgiehl @michalkleiner I rebased to remove the commit that was not required. Thanks.

[github-actions]

This issue is in "needs review" but there has been no activity for 7 days. ping @matomo-org/core-reviewers

[achakko]

@matomo-org/core-reviewers This reporting seems to be working now. The CI job ran tests and reported the UI test run results into testomat with a decent stack trace for failed tests as well. Runs can be accessed here. Once we have more data, will get meaningful results in Analytics.
https://app.testomat.io/projects/core-ui-tests/runs

[bx80]

The test tomato reporting is looking great 👍

Is there any reason the UI test output log has lots of [TESTOMATIO] Warning: Test could not be matched (404) should be possible to publish new version messages? This will make it a bit harder to check the logs, it also looks like colour highlighting has also disappeared which is helpful to quickly identify the failed tests.

[achakko]

The test tomato reporting is looking great 👍
Is there any reason the UI test output log has lots of [TESTOMATIO] Warning: Test could not be matched (404) should be possible to publish new version messages? This will make it a bit harder to check the logs, it also looks like colour highlighting has also disappeared which is helpful to quickly identify the failed tests.

Hi @bx80 I was able to remove the warnings. See one of the recent runs here. Do you think the absence of the colour highlighting is a deal breaker?

Added color = 1 and removed the deprecated Usecolors method. Seems to be working! We have a summary of any failed just above the Error message with colors ofcourse. Good to approve?

[bx80]

Thanks @achakko, much easier to read now 👍
Might be good to get additional approvals for this one, as I've not been following all the other points raised.

[achakko]

The issue with the double reporting in testomat.io is logged here. I will follow up for resolution. testomatio/reporter#245

[sgiehl]

This overall looks good to me now. Don't have access to the testomatio dashboard, so can't say if it's working on that side.