Skip to content

feat(cc-widgets): UI Automation for State Change - #476

Merged
rsarika merged 67 commits into
webex:ccwidgetsfrom
PrayagGP:ccwidgets_UserStateTest
Jul 1, 2025
Merged

feat(cc-widgets): UI Automation for State Change#476
rsarika merged 67 commits into
webex:ccwidgetsfrom
PrayagGP:ccwidgets_UserStateTest

Conversation

@PrayagGP

@PrayagGP PrayagGP commented Jun 19, 2025

Copy link
Copy Markdown
Contributor

COMPLETES #< https://jira-eng-sjc12.cisco.com/jira/browse/CAI-6521 >

This pull request addresses

UI automation for testing the user state

by making the following changes

    1. Created utility functions for tests
    2. Wrote tests for user state using the newly created utilities.

Vidcast: https://app.vidcast.io/share/1af66521-e31c-401f-9cf4-ad53e8adca43

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
  • [x ] 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 Jun 19, 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.


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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

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

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

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.

@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 labels Jun 19, 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-476.d1b38q61t1z947.amplifyapp.com

"react-dom": ">=18.3.1"
}
} No newline at end of file
}

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.

try to remove and avoid these changes

Comment thread playwright.config.ts
baseURL: 'http://localhost:3000',

/* Collect trace when retrying the failed test. See https://playwright.dev/docs/trace-viewer */
trace: 'retain-on-failure',

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 did we change this? we only want to check if itas a failure

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.

Yeah I'll revert the change. I had changed it to obtain the trace even for test success for debugging purposes just to see if things are actually happening the way I wanted them to.

Comment thread playwright/Utils/initUtils.ts Outdated
await page.locator('#select-base-triggerid').getByText('Access Token').click();
await page.getByTestId('samples:login_option_oauth').getByText('Login with Webex').click();
await page.getByTestId('login with webex button').click();
await page.getByRole('textbox', { name: 'name@example.com' }).fill(process.env.PLAYWRIGHT_USERNAME);

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.

Is it not possible to get this also by testId?

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 agree using testid will make things easier and more consistent

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.

These are buttons and textboxes for Oauth login. I don't think I can add data-testids for these as I probably won't have access to its source code.

Comment thread playwright/Utils/initUtils.ts Outdated
await page.getByTestId('samples:login_option_oauth').getByText('Login with Webex').click();
await page.getByTestId('login with webex button').click();
await page.getByRole('textbox', { name: 'name@example.com' }).fill(process.env.PLAYWRIGHT_USERNAME);
await page.getByRole('link', { name: 'Sign in' }).click();

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, can we make everything by testId?

Comment thread playwright/Utils/initUtils.ts Outdated
await page.getByTestId('multi-login-enable-checkbox').click();
}

export const initialisePage = async (page: Page): Promise<void> => {

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.

rename it to initiaseWidgets

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.

initiateWidgets or initialiseWidgets?

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.

initialiseWidgets, sounds good

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.

okay

Comment thread playwright/Utils/stateUtils.ts Outdated
dotenv.config();


export const changeState = async (page: Page, userState: string): Promise<void> => {

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.

changeUserState

Comment thread playwright/Utils/stateUtils.ts Outdated
@@ -0,0 +1,136 @@
import { Page,expect } from '@playwright/test';

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.

rename file name to userStateUtils

Comment thread playwright/Utils/stateUtils.ts Outdated
return timerText.trim();
};

export const checkConsole = async (page: Page, state: string, consoleMessages: string[]): Promise<boolean> => {

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.

rename to more meaningful name

Comment thread playwright/Utils/stationUtils.ts Outdated
@@ -0,0 +1,58 @@
import { Page } from '@playwright/test';

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.

rename file to stationLoginUtils.ts

Comment thread playwright/constants.ts Outdated
@@ -0,0 +1,23 @@
export const BASE_URL = 'http://localhost:3000';

export const STATES = {

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.

USER_STATES

@riteshfyi

Copy link
Copy Markdown
Contributor

Could you please update the pull-request.yml with the new variable names, such as PW_AGENT1_USERNAME, instead of PW_USERNAME, etc.

@rsarika
rsarika dismissed Shreyas281299’s stale review June 30, 2025 10:21

i have reviewed the comments and resolve them

@rsarika
rsarika merged commit 999cb53 into webex:ccwidgets Jul 1, 2025
7 of 8 checks passed
github-actions Bot pushed a commit that referenced this pull request Jul 1, 2025
# [1.28.0-ccwidgets.83](v1.28.0-ccwidgets.82...v1.28.0-ccwidgets.83) (2025-07-01)

### Features

* **cc-widgets:** UI Automation for State Change ([#476](#476)) ([999cb53](999cb53))
@sreenara

sreenara commented Jul 1, 2025

Copy link
Copy Markdown
Contributor

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

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.

6 participants