Bridge UI(tests): Testing workflow

[abheektripathy]

we should have unit tests running on the core bridging and claim flow. They should be run on every pr to verify the new changes aren't breaking any older flows.

Hooks we're targeting as of now --

• useBridge.tsx
• useClaim.tsx~~

[abheektripathy]

according to the discussion yesterday, just writing unit tests wouldn't help in itself, here's how the testing workflow should go-

• setup winston / logger, add logs where required
• setup a simple dashboard to display those logs @moraesjeremias
• setup monitors based on if a / few particular error see spikes

will be tracked in a new issue considering the work.

• Bridge UI(tests) using nightwatch write a e2e test that mocks the user flow and runs on every new PR. #64

[moraesjeremias]

Report

• A tmp dashboard was set to report error and general bridge UI client side metrics

Blockers

• Current env label is wrong. Needs to troubleshoot it and find root cause.

PRs:

• feat: Adds DD log lib #60

[moraesjeremias]

Report

• The labeling issue root cause was that NODE_ENV is an enum that only takes <test|development|production> values. Switched to NEXT_PUBLIC_ENVIRONMENT to have more flexibility/fine grain control.

Contract

Agreed with @abheektripathy the following log env label values:

production -> Main Branch
staging -> Staging Branch
test -> Preview Branch
local -> Local branch (uncommited changes)

PRs:

• fix: change env var for setting logs env #69

[abheektripathy]

@moraesjeremias marking this as done, since we have the monitors setup for failed claims, writing tests using nightwatch would be tracked in a separate issue.