Skip to content
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

Fixed the user fixtures in cypress test #10442

Merged
merged 1 commit into from
Feb 6, 2025
Merged

Conversation

nihal467
Copy link
Member

@nihal467 nihal467 commented Feb 6, 2025

Proposed Changes

  • Fixes #issue_number
  • Change 1
  • Change 2
  • More?

@ohcnetwork/care-fe-code-reviewers

Merge Checklist

  • Add specs that demonstrate bug / test a new feature.
  • Update product documentation.
  • Ensure that UI text is kept in I18n files.
  • Prep screenshot or demo video for changelog entry, and attach it to issue.
  • Request for Peer Reviews
  • Completion of QA

Summary by CodeRabbit

  • Tests
    • Refined automated authentication for patient management by switching to a dedicated test account.
    • Introduced a new test user with tailored credentials to ensure more effective testing of patient-related workflows.

@nihal467 nihal467 requested a review from a team as a code owner February 6, 2025 07:23
Copy link
Contributor

coderabbitai bot commented Feb 6, 2025

Walkthrough

This pull request updates the authentication process in the Cypress test suite for patient management. The login credentials within the test are changed from using the "doctor" role to "devdoctor". Correspondingly, a new user entry for "devdoctor" is added in the fixtures file with specific credentials. The changes are confined to test automation files and do not affect the control flow or the public API.

Changes

File(s) Change Summary
cypress/e2e/.../patient_details.cy.ts Updated login call in the beforeEach hook from cy.loginByApi("doctor") to cy.loginByApi("devdoctor").
cypress/fixtures/users.json Added a new user entry for "devdoctor" with "username": "developdoctor" and "password": "Test@123".

Sequence Diagram(s)

sequenceDiagram
    participant TS as Test Suite
    participant API as Authentication API
    participant PM as Patient Management Module
    
    TS->>API: cy.loginByApi("devdoctor")
    API-->>TS: Auth token
    TS->>PM: Fetch patient details
Loading

Possibly related PRs

Suggested labels

needs review, tested

Suggested reviewers

  • rithviknishad
  • khavinshankar

Poem

I'm a little rabbit, quick on my feet,
Hopping through code, where tests and users meet.
Devdoctor leads with a fresh new tune,
In our testing garden beneath the digital moon.
Carrots and credentials make our progress sweet! 🥕

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

Deploying care-fe with  Cloudflare Pages  Cloudflare Pages

Latest commit: 3ed2e14
Status: ✅  Deploy successful!
Preview URL: https://78680770.care-fe.pages.dev
Branch Preview URL: https://cypress-fixtures.care-fe.pages.dev

View logs

Copy link

netlify bot commented Feb 6, 2025

Deploy Preview for care-ohc ready!

Name Link
🔨 Latest commit 3ed2e14
🔍 Latest deploy log https://app.netlify.com/sites/care-ohc/deploys/67a46377e373cb0008498396
😎 Deploy Preview https://deploy-preview-10442--care-ohc.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
cypress/e2e/patient_spec/patient_details.cy.ts (1)

10-13: Consider moving login to before hook.

Based on previous learnings from PR #10287, when using cy.session, a single loginByApi call in the before hook is sufficient as Cypress automatically handles session creation and restoration. Additional login calls in beforeEach are redundant.

 describe("Patient Management", () => {
+  before(() => {
+    cy.loginByApi("devdoctor");
+  });
+
   beforeEach(() => {
-    cy.loginByApi("devdoctor");
     cy.visit("/");
   });
cypress/fixtures/users.json (1)

22-24: Consider following consistent username format.

While the new user entry is good, consider following the hyphenated format used by other test users (e.g., "nihal-nurse", "arjun-doctor") for consistency.

   "devdoctor": {
-    "username": "developdoctor",
+    "username": "dev-doctor",
     "password": "Test@123"
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d827058 and 3ed2e14.

📒 Files selected for processing (2)
  • cypress/e2e/patient_spec/patient_details.cy.ts (1 hunks)
  • cypress/fixtures/users.json (1 hunks)
🧰 Additional context used
📓 Learnings (1)
cypress/e2e/patient_spec/patient_details.cy.ts (2)
Learnt from: nihal467
PR: ohcnetwork/care_fe#9285
File: cypress/e2e/patient_spec/PatientDoctorNotes.cy.ts:17-17
Timestamp: 2024-12-04T07:06:49.613Z
Learning: In `PatientDoctorNotes.cy.ts`, the login methods `loginManuallyAsNurse()` and `loginByRole("nurse")` serve different purposes and approaches. Refactoring `loginManuallyAsNurse()` to use `loginByRole()` is not necessary in this context.
Learnt from: nihal467
PR: ohcnetwork/care_fe#10287
File: cypress/e2e/patient_spec/patient_creation.cy.ts:102-109
Timestamp: 2025-01-30T11:35:56.668Z
Learning: In Cypress tests, when using `cy.session`, a single `loginByApi` call in the `before` hook is sufficient as Cypress automatically handles session creation and restoration. Additional login calls in `beforeEach` are redundant.
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: cypress-run (1)
🔇 Additional comments (1)
cypress/e2e/patient_spec/patient_details.cy.ts (1)

11-11: LGTM! Role change looks good.

The change from "doctor" to "devdoctor" aligns with the updated user fixtures.

Copy link

cypress bot commented Feb 6, 2025

CARE    Run #4655

Run Properties:  status check passed Passed #4655  •  git commit 3ed2e14773: Fixed the user fixtures in cypress test
Project CARE
Branch Review cypress-fixtures
Run status status check passed Passed #4655
Run duration 06m 23s
Commit git commit 3ed2e14773: Fixed the user fixtures in cypress test
Committer Mohammed Nihal
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 0
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 11
View all changes introduced in this branch ↗︎

@rithviknishad rithviknishad merged commit 3e0bbc4 into develop Feb 6, 2025
23 checks passed
@rithviknishad rithviknishad deleted the cypress-fixtures branch February 6, 2025 07:31
Copy link

github-actions bot commented Feb 6, 2025

@nihal467 Your efforts have helped advance digital healthcare and TeleICU systems. 🚀 Thank you for taking the time out to make CARE better. We hope you continue to innovate and contribute; your impact is immense! 🙌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants