chore(tests): Add credentials table test

[jan-law]

Related #403

Adds unit tests for the Stored JMX Credentials Table and some refactoring to allow Jest access to the table components via imports and component labels.

You'll notice that the enums in StoreJmxCredentials were changed to "'TargetCredentialsStored' as NotificationCategory.TargetCredentialsStored". This is a workaround due to the fact that Jest doesn't support exported const enums when testing (link to issue)
Nevermind, fixed the messageKeys import by adding ...jest.requireActual('@app/Shared/Services/NotificationChannel.service'), to the mocked NotificationChannel service.

To make the tests easier to read, I also split up the 'Delete credentials' test case into two tests, ie 'removes the correct table entry when a deletion notification is received' and 'makes a delete request when deleting one credential'. The first test receives a mocked notification before asserting that the table state was updated, and the second test clicks the Add/Delete button before asserting that the API calls were made. (The equivalent API call assertion for adding stored credentials isn't tested here because the call is made in AuthModal.)

[hareetd]

Looks good!

Judging from your mock on line 94, it seems the NotificationChannel.messages subscription is invoked three times in StoreJmxCredentials. For my own understanding, could you explain why this happens? I thought there would be only two invocations (one for a stored notification and the other for a deleted notification) once the render is complete and the useEffect calls are triggered.

[andrewazores]

Check on that latest commit please - the package-lock.json exploded.

[jan-law]

I rebased my last commit and removed the extra dependencies - it turns out that you don't need dynamic importing for jest.doMock to work unless you are specifically using import("../components/Component") inside your tests.

[andrewazores]

@jan-law ready to merge?

[jan-law]

yes, ready to merge