Skip to content

Fix K6 stress/spike test recording booleans instead of actual HTTP duration#123

Merged
Senthil455 merged 7 commits into
mainfrom
fix/issue-50-k6-metrics
Jun 17, 2026
Merged

Fix K6 stress/spike test recording booleans instead of actual HTTP duration#123
Senthil455 merged 7 commits into
mainfrom
fix/issue-50-k6-metrics

Conversation

@Senthil455

Copy link
Copy Markdown
Owner

Fix k6-stress.js recording boolean (1/0) for login_duration instead of actual login HTTP request timing. Inlines the getToken() function so the login response timings are captured. Also fixes k6-spike.js similarly and uses explicit 0/1 for Rate metrics.

Add backup_codes_shown flag to user_mfa table. Backup codes are only
returned on the initial setup request and marked as shown afterwards.
Re-running setup will regenerate codes but not display them. Add a
/mfa/rotate-backup-codes endpoint that requires current TOTP token
to view new backup codes.
Prevent token leak by removing the raw passwordless token from the API
response body. The token is still stored hashed in the database and can
be verified via /auth/passwordless/verify. The response now only returns
a generic success message.
Replace 4 fragile regex patterns for extracting NameID and SAML attribute
values with robust DOM-based extraction using the already-parsed XML
document. This fixes namespace sensitivity, encoding variations, and
CDATA handling issues. Also moves the DOMParser outside the
SAML_IDP_CERT conditional so it is always available for attribute
extraction.
Add internal auth token to test clients for ai-copilot-service and
ats-service so integration tests pass instead of returning 401.
Fix employee-service main.py to use os.environ.get() for MONGO_USER,
MONGO_PASSWORD, INTERNAL_KEY, and RABBITMQ_USER instead of bracket
access that raises KeyError when env vars are not set.
Fix k6-stress.js recording boolean (1/0) instead of actual login HTTP
request duration for login_duration metric. Fix both k6-stress.js and
k6-spike.js to inline the login request to capture response timings
and use explicit 0/1 for Rate metrics.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant