feat(ci): run UI e2e tests

[crenshaw-dev]

Looked the the ui-test directory was mostly going unused. I got the tests working in CI, so hopefully that'll make the tests more useful.

[bunnyshell[bot]]

:exclamation: Preview Environment undeploy from Bunnyshell failed

See: Environment Details | Pipeline Logs

Available commands (reply to this comment):

• :rocket: /bns:deploy to redeploy the environment
• :x: /bns:delete to try again to remove the environment

[bunnyshell[bot]]

:white_check_mark: Preview Environment created on Bunnyshell but will not be auto-deployed

See: Environment Details

Available commands (reply to this comment):

• :rocket: /bns:deploy to deploy the environment

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 49.36%. Comparing base (48551b3) to head (78007da). Report is 5 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #20200      +/-   ##
==========================================
- Coverage   55.89%   49.36%   -6.54%     
==========================================
  Files         322      322              
  Lines       44499    44499              
==========================================
- Hits        24874    21966    -2908     
- Misses      17057    20048    +2991     
+ Partials     2568     2485      -83     

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[crenshaw-dev]

Based on codecov output, looks like I managed to prevent coverage being reported from e2e tests. 0_o

[nitishfy]

@crenshaw-dev I'm curious to know how did you test those changes out for the CI before raising the PR?

[crenshaw-dev]

@nitishfy I removed all the conditions that block running this in my fork and added the option to trigger it manually. After testing, I reverted those changes.

[nitishfy]

@nitishfy I removed all the conditions that block running this in my fork and added the option to trigger it manually. After testing, I reverted those changes.

Ah nice, this is a good approach.