Skip to content

test: Added branding related test for the community user#38460

Merged
sagar-qa007 merged 2 commits intoreleasefrom
fix/adminsettingimage
Jan 3, 2025
Merged

test: Added branding related test for the community user#38460
sagar-qa007 merged 2 commits intoreleasefrom
fix/adminsettingimage

Conversation

@sagar-qa007
Copy link
Contributor

@sagar-qa007 sagar-qa007 commented Jan 3, 2025

Description

Admin setting Test case for branding

Fixes # https://app.zenhub.com/workspaces/stability-pod-6690c4814e31602e25cab7fd/issues/gh/appsmithorg/appsmith/38459

Automation

/ok-to-test tags="@tag.Settings,@tag.Sanity"

🔍 Cypress test results

Tip

🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/12593006493
Commit: 7e05339
Cypress dashboard.
Tags: @tag.Settings,@tag.Sanity
Spec:


Fri, 03 Jan 2025 08:28:02 UTC

Communication

Should the DevRel and Marketing teams inform users about this change?

  • Yes
  • No

Summary by CodeRabbit

  • Tests

    • Added a new Cypress test suite for validating Admin Branding Page settings
    • Implemented test case for verifying branding data updates for community users
    • Tested logo and favicon uploads in various image formats
  • Locators

    • Added multiple new locators for Admin Settings UI elements
    • Introduced locators for branding, authentication, and application management interfaces

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 3, 2025

Walkthrough

This pull request introduces a new Cypress test suite for validating branding settings in the Admin Settings page. The changes include a comprehensive test case that checks logo and favicon uploads across different file formats, verifies UI element visibility, and ensures proper logo display. Simultaneously, the AdminsSettings.js locator file is expanded with numerous new properties to support these testing and UI interaction scenarios.

Changes

File Change Summary
app/client/cypress/e2e/Regression/ClientSide/AdminSettings/Branding_settings_Spec.ts Added new test suite for Admin Branding Page with comprehensive logo and favicon upload validations
app/client/cypress/locators/AdminsSettings.js Added multiple new locator properties for branding, authentication, and application management UI elements

Possibly related PRs

Suggested labels

Test, Templates Product, Widgets & Accelerators Pod

Suggested reviewers

  • ApekshaBhosale
  • NandanAnantharamu

Poem

🎨 Branding's dance, a pixel's grace
Logos leap from file to space
Cypress clicks with testing might
Settings bloom in digital light
A brand new world, just one upload away! 🚀


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

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.

@github-actions github-actions bot added skip-changelog Adding this label to a PR prevents it from being listed in the changelog Test labels Jan 3, 2025
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: 1

🧹 Nitpick comments (1)
app/client/cypress/locators/AdminsSettings.js (1)

50-72: Consider using data- attributes for selectors.*

The code here uses CSS classes (like ".t--settings-category-branding") for selectors. Although this seems consistent with the existing code, the guidelines recommend using data-* attributes to ensure stable and maintainable selectors.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0198ad8 and 7e05339.

⛔ Files ignored due to path filters (4)
  • app/client/cypress/fixtures/appsmith-community-logo.svg is excluded by !**/*.svg
  • app/client/cypress/fixtures/branding_sample.png is excluded by !**/*.png
  • app/client/cypress/fixtures/branding_sampleICO.ico is excluded by !**/*.ico
  • app/client/cypress/fixtures/branding_samplejpg.jpg is excluded by !**/*.jpg
📒 Files selected for processing (2)
  • app/client/cypress/e2e/Regression/ClientSide/AdminSettings/Branding_settings_Spec.ts (1 hunks)
  • app/client/cypress/locators/AdminsSettings.js (1 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
app/client/cypress/e2e/Regression/ClientSide/AdminSettings/Branding_settings_Spec.ts (1)

Pattern app/client/cypress/**/**.*: Review the following e2e test code written using the Cypress test library. Ensure that:

  • Follow best practices for Cypress code and e2e automation.
  • Avoid using cy.wait in code.
  • Avoid using cy.pause in code.
  • Avoid using agHelper.sleep().
  • Use locator variables for locators and do not use plain strings.
  • Use data-* attributes for selectors.
  • Avoid Xpaths, Attributes and CSS path.
  • Avoid selectors like .btn.submit or button[type=submit].
  • Perform logins via API with LoginFromAPI.
  • Perform logout via API with LogOutviaAPI.
  • Perform signup via API with SignupFromAPI.
  • Avoid using it.only.
  • Avoid using after and aftereach in test cases.
  • Use multiple assertions for expect statements.
  • Avoid using strings for assertions.
  • Do not use duplicate filenames even with different paths.
  • Avoid using agHelper.Sleep, this.Sleep in any file in code.
app/client/cypress/locators/AdminsSettings.js (1)

Pattern app/client/cypress/**/**.*: Review the following e2e test code written using the Cypress test library. Ensure that:

  • Follow best practices for Cypress code and e2e automation.
  • Avoid using cy.wait in code.
  • Avoid using cy.pause in code.
  • Avoid using agHelper.sleep().
  • Use locator variables for locators and do not use plain strings.
  • Use data-* attributes for selectors.
  • Avoid Xpaths, Attributes and CSS path.
  • Avoid selectors like .btn.submit or button[type=submit].
  • Perform logins via API with LoginFromAPI.
  • Perform logout via API with LogOutviaAPI.
  • Perform signup via API with SignupFromAPI.
  • Avoid using it.only.
  • Avoid using after and aftereach in test cases.
  • Use multiple assertions for expect statements.
  • Avoid using strings for assertions.
  • Do not use duplicate filenames even with different paths.
  • Avoid using agHelper.Sleep, this.Sleep in any file in code.
🔇 Additional comments (1)
app/client/cypress/e2e/Regression/ClientSide/AdminSettings/Branding_settings_Spec.ts (1)

1-108: Well-structured Cypress test suite.

No forbidden usage (like cy.wait, cy.pause, or it.only) is found; consistent use of external locators for UI elements is effective. Good job!

loginContainer: ".t--login-container",
signupLink: ".t--signup-link",
authContainer: ".t--auth-container",
submitButton: "button[type='submit']",
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Avoid using button[type='submit'] as a selector.

According to the guidelines, please replace this with a data-* based attribute to ensure robust and maintainable selectors.

- submitButton: "button[type='submit']",
+ submitButton: "[data-testid='t--submit-button']",
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
submitButton: "button[type='submit']",
submitButton: "[data-testid='t--submit-button']",

@sagar-qa007 sagar-qa007 added the ok-to-test Required label for CI label Jan 3, 2025
Copy link
Contributor

@NandanAnantharamu NandanAnantharamu left a comment

Choose a reason for hiding this comment

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

Lgtm

@sagar-qa007 sagar-qa007 merged commit 28d35ad into release Jan 3, 2025
@sagar-qa007 sagar-qa007 deleted the fix/adminsettingimage branch January 3, 2025 12:29
@coderabbitai coderabbitai bot mentioned this pull request Jan 16, 2025
2 tasks
github-actions bot pushed a commit to Zeral-Zhang/appsmith that referenced this pull request Feb 7, 2025
…#38460)

## Description
Admin setting Test case for branding


Fixes #
https://app.zenhub.com/workspaces/stability-pod-6690c4814e31602e25cab7fd/issues/gh/appsmithorg/appsmith/38459

## Automation

/ok-to-test tags="@tag.Settings,@tag.Sanity"

### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results  -->
> [!TIP]
> 🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/12593006493>
> Commit: 7e05339
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=12593006493&attempt=2"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Settings,@tag.Sanity`
> Spec:
> <hr>Fri, 03 Jan 2025 08:28:02 UTC
<!-- end of auto-generated comment: Cypress test results  -->


## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [x] No


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Tests**
- Added a new Cypress test suite for validating Admin Branding Page
settings
- Implemented test case for verifying branding data updates for
community users
	- Tested logo and favicon uploads in various image formats

- **Locators**
	- Added multiple new locators for Admin Settings UI elements
- Introduced locators for branding, authentication, and application
management interfaces

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ok-to-test Required label for CI skip-changelog Adding this label to a PR prevents it from being listed in the changelog Test

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants