Skip to content

fix(cc-widgets): End 2 End Tests stabilised #517

Merged
mkesavan13 merged 27 commits into
webex:ccwidgetsfrom
rsarika:e2e-fixes
Aug 22, 2025
Merged

fix(cc-widgets): End 2 End Tests stabilised #517
mkesavan13 merged 27 commits into
webex:ccwidgetsfrom
rsarika:e2e-fixes

Conversation

@rsarika

@rsarika rsarika commented Aug 15, 2025

Copy link
Copy Markdown
Contributor

COMPLETES #https://jira-eng-sjc12.cisco.com/jira/browse/CAI-6525

This pull request addresses

refactoring e2e tests to make them stable and reduce execution time.

by making the following changes

created a testmanager to have all the apge setup logic at one place.
updated config with 5 threads(workers
).

Screenshot 2025-08-19 at 9 16 15 AM

Change Type

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Tooling change
  • Internal code refactor

The following scenarios were tested

  • The testing is done with the amplify link
    < ENUMERATE TESTS PERFORMED, WHETHER MANUAL OR AUTOMATED >

The GAI Coding Policy And Copyright Annotation Best Practices

  • GAI was not used (or, no additional notation is required)
  • Code was generated entirely by GAI
  • GAI was used to create a draft that was subsequently customized or modified
  • Coder created a draft manually that was non-substantively modified by GAI (e.g., refactoring was performed by GAI on manually written code)
  • Tool used for AI assistance (GitHub Copilot / Other - specify)
    • Github Copilot
    • Other - Please Specify
  • This PR is related to
    • Feature
    • Defect fix
    • Tech Debt
    • Automation

Checklist before merging

  • I have not skipped any automated checks
  • All existing and new tests passed
  • I have updated the testing document

@coderabbitai

coderabbitai Bot commented Aug 15, 2025

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

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.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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.

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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.

@rsarika rsarika added the validated Indicates that the PR is ready for actions label Aug 15, 2025
@aws-amplify-us-east-2

Copy link
Copy Markdown

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-517.d1b38q61t1z947.amplifyapp.com

@rsarika rsarika added the run_e2e Add this label to run E2E test for meeting and CC widgets label Aug 19, 2025
@rsarika rsarika changed the title fix: End 2 End Tests stabilised fix(cc-widgets): End 2 End Tests stabilised Aug 19, 2025
@rsarika rsarika added validated Indicates that the PR is ready for actions run_e2e Add this label to run E2E test for meeting and CC widgets and removed validated Indicates that the PR is ready for actions run_e2e Add this label to run E2E test for meeting and CC widgets labels Aug 19, 2025
@Shreyas281299

Copy link
Copy Markdown
Contributor

@CodeRabbit review

@Shreyas281299 Shreyas281299 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks for this. I really like these changes for timeouts and the suites.
Just some minor changes request. But mostly this looks good

Comment thread playwright/README.md Outdated
Comment on lines +172 to +173
npx playwright test --grep "@chat" # Chat tests only
npx playwright test --grep "@telephony" # Voice tests only

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Do we have this feature? I tried running this locally and it doesnt get any tests, fails with no test found. I think we can remove this part of filter by tag.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

addressed updated this section properly

Comment thread playwright/constants.ts Outdated
EXTENSION: 'extension',
CHAT: 'chat',
MULTI_SESSION: 'multiSession',
} as const;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I dont think we need this as const in the above two objects

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

addressed

Comment thread playwright/constants.ts Outdated
CHAT_EMAIL: 'playwright@test.com',
EMAIL_TEXT: '--This Email is generated due to playwright automation test for incoming Tasks---',
EXTENSION_CALL_INDICATOR: 'Ringing...',
} as const;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Same here

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

addressed

Comment thread playwright/global.setup.ts Outdated
fs.writeFileSync(envPath, envContent, 'utf8');
}

module.exports = {UpdateENVWithUserSets};

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Why are we exporting like this? We can just put export const function

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

addressed

Comment thread playwright/global.setup.ts Outdated
}
});

UpdateENVWithUserSets();

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Rather than here, Can we put this inside the setup('OAuth') step?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

addressed

@mkesavan13 mkesavan13 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Please address the review comments by both me and Shreyas.

Rest looks good

Comment thread playwright.config.ts Outdated
name: 'Test: Chrome',
// Run all tests except advanced tests and transfer/consult tests on Chrome
testIgnore: [/advanced-task-controls-test\.spec\.ts/],
name: 'SET_1',

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Can we have one config JSON and then loop them through for all these projects? That way, we need not modify any same config for 5 times or more in future?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

great suggestion. addressed by moving the suite file name to testdata and reading threads and projects from testdata dynamically.

Comment thread playwright.config.ts Outdated
workers: 1,
/* Reporter to use. See https://playwright.dev/docs/test-reporters */
fullyParallel: true,
workers: 5,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Should we have 6 workers considering OAuth: Get Access Token being one of the projects?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

OAuth: Get Access Token, is the dependency for all the projects . so it should complete before any project starts.

@mkesavan13
mkesavan13 merged commit 4dd2f74 into webex:ccwidgets Aug 22, 2025
12 of 15 checks passed
github-actions Bot pushed a commit that referenced this pull request Aug 22, 2025
# [1.28.0-ccwidgets.110](v1.28.0-ccwidgets.109...v1.28.0-ccwidgets.110) (2025-08-22)

### Bug Fixes

* **cc-widgets:** End 2 End Tests stabilised  ([#517](#517)) ([4dd2f74](4dd2f74))
@sreenara

Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 1.28.0-ccwidgets.110 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

released on @ccwidgets run_e2e Add this label to run E2E test for meeting and CC widgets validated Indicates that the PR is ready for actions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants