Daniel Nephin 447097b166 ca: make test naming consistent
While working on the CA system it is important to be able to run all the
tests related to the system, without having to wait for unrelated tests.
There are many slow and unrelated tests in agent/consul, so we need some
way to filter to only the relevant tests.

This PR renames all the CA system related tests to start with either
`TestCAMananger` for tests of internal operations that don't have RPC
endpoint, or `TestConnectCA` for tests of RPC endpoints. This allows us
to run all the test with:

    go test -run 'TestCAMananger|TestConnectCA' ./agent/consul

The test naming follows an undocumented convention of naming tests as
follows:

    Test[<struct name>_]<function name>[_<test case description>]

I tried to always keep Primary/Secondary at the end of the description,
and _Vault_ has to be in the middle because of our regex to run those
tests as a separate CI job.

You may notice some of the test names changed quite a bit. I did my best
to identify the underlying method being tested, but I may have been
slightly off in some cases.
2021-12-02 14:57:09 -05:00
..
2021-11-16 12:04:01 -06:00
2021-11-16 12:04:01 -06:00
2021-12-02 14:57:09 -05:00
2021-11-16 12:04:01 -06:00
2021-11-01 11:40:16 -04:00
2021-11-16 12:04:01 -06:00
2021-11-16 12:04:01 -06:00
2021-11-16 12:04:01 -06:00
2021-12-01 14:56:10 -05:00
2021-11-16 12:04:01 -06:00
2021-11-16 12:04:01 -06:00
2021-11-16 12:04:01 -06:00
2021-11-16 12:04:01 -06:00
2021-09-03 09:12:03 -04:00
2021-11-16 12:04:01 -06:00
2021-11-16 12:04:01 -06:00
2021-08-26 14:06:49 -04:00