-
Notifications
You must be signed in to change notification settings - Fork 103
feat(user): implement BDD e2e tests for registration #542
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
Not able to understand the format of the confirmation message after signup. yarn bdd:e2e - test status Execution of 9 workers started at 2025-08-30T10:29:22.617Z [0-7] RUNNING in chrome - file:///features/register.feature "spec" Reporter:[chrome 139.0.7258.155 mac #0-6] Running: chrome (v139.0.7258.155) on mac
|
|
@abhiram-art did you set up the keycloak api key in the user api side? As we mentioned here: https://greenstand.slack.com/archives/C05TVUSEQQ0/p1755746182523629 |
|
@abhiram-art The key PRIVATE_KEYCLOAK_CLIENT_SECRET is supposed to be private, right? |
|
@dadiorchen yes, I entered the client secret while setting up the project at the beginning. |
Description
This PR completes the BDD end-to-end test scenario for user registration, as described in issue #520.
It connects the frontend and backend layers through WebDriverIO and finalizes the register.feature flow to ensure the user registration journey is properly tested end-to-end using Behavior Driven Development (BDD) style.
Fixes: #520
Changes Made
Changes in
appsfolder (specify the app and briefly describe thechanges):
WebNativeBDDUpdated register.feature with a complete scenario for registering a new user using email
Implemented corresponding step definitions in step-definitions/steps.ts:
- Navigation to register page
- Ensuring the test email is not already registered
- Filling out and submitting the form.
Verifying confirmation message
packagesfolder (specify the package and briefly describethe changes):
CoreType of Change
functionality to not work as expected)
Screenshots
How Has This Been Tested?
Checklist:
Additional Comments
Please review the error for the confirmation message test.