Skip to content

testing(ui): set up cypress#1712

Closed
davdhacs wants to merge 18 commits intomasterfrom
rox-29520-start-ui-tests
Closed

testing(ui): set up cypress#1712
davdhacs wants to merge 18 commits intomasterfrom
rox-29520-start-ui-tests

Conversation

@davdhacs
Copy link
Copy Markdown
Contributor

@davdhacs davdhacs commented Nov 17, 2025 •
edited
Loading

Set up UI testing

  • Add cypress testing
  • Make a local backend deployment (no auth, not https)

Written by claude(claude-sonnet-4-5@20250929).
Minor changes by me.

davdhacs and others added 8 commits November 11, 2025 22:13
@davdhacs
start cypress
8d470f3
@davdhacs
testmode no auth
9f1727b
@davdhacs
add cypress to package
eeb9adc
@davdhacs
add deploy-local.sh
a9427bb
@davdhacs
move local deploy into make+helm.sh
3d11c37
@davdhacs
add local env as an option
d3fda41
@davdhacs @claude
Fix secrets.yaml template syntax and format Cypress README
90b73ae 
- Fix oidc.yaml template syntax error in secrets.yaml
- Fix TLS cert/key base64 encoding (use b64enc instead of nindent)
- Format README_CYPRESS.md with Prettier to pass lint-check

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
@davdhacs
use http for test_mode
134edd2
@davdhacs davdhacs mentioned this pull request Nov 19, 2025
Closed
@rhacs-bot
Copy link
Copy Markdown
Contributor

rhacs-bot commented Nov 20, 2025

A single node development cluster (infra-pr-1712) was allocated in production infra for this PR.

CI will attempt to deploy quay.io/rhacs-eng/infra-server: to it.

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-1712 --zone us-central1-a --project acs-team-temp-dev

🛠️ And pull infractl from the deployed dev infra-server with:

nohup kubectl -n infra port-forward svc/infra-server-service 8443:8443 &
make pull-infractl-from-dev-server

🚲 You can then use the dev infra instance e.g.:

bin/infractl -k -e localhost:8443 whoami

⚠️ Any clusters that you start using your dev infra instance should have a lifespan shorter then the development cluster instance. Otherwise they will not be destroyed when the dev infra instance ceases to exist when the development cluster is deleted. ⚠️

Further Development

☕ If you make changes, you can commit and push and CI will take care of updating the development cluster.

🚀 If you only modify configuration (chart/infra-server/configuration) or templates (chart/infra-server/{static,templates}), you can get a faster update with:

make helm-deploy

Logs

Logs for the development infra depending on your @redhat.com authuser:

Or:

kubectl -n infra logs -l app=infra-server --tail=1 -f

@davdhacs davdhacs closed this Dec 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@pedrottimark pedrottimark Awaiting requested review from pedrottimark

@rhacs-bot rhacs-bot Awaiting requested review from rhacs-bot rhacs-bot will be requested when the pull request is marked ready for review rhacs-bot is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@davdhacs @rhacs-bot