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

New Cypress Test for HCX Workflow in the platform #9007

Draft
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

nihal467
Copy link
Member

@nihal467 nihal467 commented Nov 5, 2024

Proposed Changes

@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

Copy link

coderabbitai bot commented Nov 5, 2024

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


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 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

netlify bot commented Nov 5, 2024

Deploy Preview for care-ohc ready!

Name Link
🔨 Latest commit 0a39eb2
🔍 Latest deploy log https://app.netlify.com/sites/care-ohc/deploys/672a61e861cfec0008618d93
😎 Deploy Preview https://deploy-preview-9007--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

Deploying care-fe with  Cloudflare Pages  Cloudflare Pages

Latest commit: 0a39eb2
Status: ✅  Deploy successful!
Preview URL: https://7cc8f259.care-fe.pages.dev
Branch Preview URL: https://hcx-develop.care-fe.pages.dev

View logs

Copy link

cypress bot commented Nov 5, 2024

CARE    Run #3809

Run Properties:  status check failed Failed #3809  •  git commit 0a39eb2472: New Cypress Test for HCX Workflow in the platform
Project CARE
Branch Review hcx-develop
Run status status check failed Failed #3809
Run duration 06m 42s
Commit git commit 0a39eb2472: New Cypress Test for HCX Workflow in the platform
Committer Mohammed Nihal
View all properties for this run ↗︎

Test results
Tests that failed  Failures 11
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 115
View all changes introduced in this branch ↗︎

Tests for review

Failed  hcx_spec/HcxClaims.cy.ts • 1 failed test • UI-Chrome

View Output

Test Artifacts
HCX Claims configuration and approval workflow > Verify the HCX Workflow for a patient Test Replay Screenshots
Failed  patient_spec/PatientLogUpdate.cy.ts • 3 failed tests • UI-Chrome

View Output

Test Artifacts
Patient Log Update in Normal, Critical and TeleIcu > Create a new TeleIcu log update for a domicilary care patient Test Replay Screenshots
Patient Log Update in Normal, Critical and TeleIcu > Create a new Normal Log update for a domicilary care patient and edit it Test Replay Screenshots
Patient Log Update in Normal, Critical and TeleIcu > Create a Normal Log update to verify MEWS Score Functionality Test Replay Screenshots
Failed  patient_spec/PatientConsultationCreation.cy.ts • 1 failed test • UI-Chrome

View Output

Test Artifacts
Patient Consultation in multiple combination > Edit created consultation to existing patient Test Replay Screenshots
Failed  patient_spec/PatientRegistration.cy.ts • 1 failed test • UI-Chrome

View Output

Test Artifacts
Patient Creation with consultation > Edit the patient details with no consultation and verify Test Replay Screenshots
Failed  patient_spec/PatientConsultationDischarge.cy.ts • 4 failed tests • UI-Chrome

View Output

Test Artifacts
Patient Discharge based on multiple reason > Discharge a LAMA patient in the consultation Test Replay Screenshots
Patient Discharge based on multiple reason > Discharge a expired patient in the consultation Test Replay Screenshots
Patient Discharge based on multiple reason > Discharge patient with referred reason to a facility Test Replay Screenshots
Patient Discharge based on multiple reason > Discharge a recovered patient with all relevant fields Test Replay Screenshots

The first 5 failed specs are shown, see all 6 specs in Cypress Cloud.

Copy link

github-actions bot commented Nov 6, 2024

👋 Hi, @nihal467,
Conflicts have been detected against the base branch. Please rebase your branch against the base branch.


This message is automatically generated by prince-chrismc/label-merge-conflicts-action so don't hesitate to report issues/improvements there.

@github-actions github-actions bot added the merge conflict pull requests with merge conflict label Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merge conflict pull requests with merge conflict
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add cypress test for HCX workflow
1 participant