-
Notifications
You must be signed in to change notification settings - Fork 73
Add E2E tests for Workloads/Cronjob in the dashboard #257
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
Add E2E tests for Workloads/Cronjob in the dashboard #257
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @SunsetB612, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request significantly refactors the dashboard's End-to-End testing suite. The focus has shifted from testing Namespace management functionalities to establishing E2E coverage for Workloads, specifically Cronjobs. This change also introduces the capability for E2E tests to interact directly with the Kubernetes API, enhancing the reliability and scope of automated testing.
Highlights
- Removed Namespace E2E Tests: All existing End-to-End (E2E) tests related to Namespace creation, deletion, and network error handling have been removed from the dashboard's test suite.
- Added Cronjob E2E List Test: The E2E test for listing Namespaces has been refactored and repurposed to now test the listing functionality for Cronjobs within the dashboard's Workloads section.
- Introduced Kubernetes Client Library: The
@kubernetes/client-nodelibrary has been added as a dependency, enabling more direct programmatic interaction with Kubernetes APIs within the E2E test environment. This suggests a more robust approach to test setup and verification.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces end-to-end tests for the CronJob workload in the dashboard. It achieves this by repurposing an existing namespace test file and removing other obsolete namespace-related tests. Additionally, it updates dependencies, notably adding @kubernetes/client-node. My review focuses on improving the maintainability of the new test code. I've suggested changes to variable names and comments to make them more accurate and less confusing.
| // 点击可见的 Statefulset tab | ||
| const statefulsetTab = page.locator('role=option[name="Cronjob"]'); | ||
| await statefulsetTab.waitFor({ state: 'visible', timeout: 30000 }); | ||
| await statefulsetTab.click(); | ||
|
|
||
| // 验证选中状态 | ||
| await expect(statefulsetTab).toHaveAttribute('aria-selected', 'true'); | ||
|
|
||
|
|
||
| // 验证 StatefulSet 列表表格可见 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The variable name statefulsetTab is misleading as it's being used to locate the 'Cronjob' tab. The comments in this block are also inconsistent, referring to 'Statefulset' instead of 'Cronjob'. To improve code clarity and maintainability, I suggest renaming the variable to cronjobTab and updating the comments to correctly refer to 'Cronjob'.
| // 点击可见的 Statefulset tab | |
| const statefulsetTab = page.locator('role=option[name="Cronjob"]'); | |
| await statefulsetTab.waitFor({ state: 'visible', timeout: 30000 }); | |
| await statefulsetTab.click(); | |
| // 验证选中状态 | |
| await expect(statefulsetTab).toHaveAttribute('aria-selected', 'true'); | |
| // 验证 StatefulSet 列表表格可见 | |
| // 点击可见的 Cronjob tab | |
| const cronjobTab = page.locator('role=option[name="Cronjob"]'); | |
| await cronjobTab.waitFor({ state: 'visible', timeout: 30000 }); | |
| await cronjobTab.click(); | |
| // 验证选中状态 | |
| await expect(cronjobTab).toHaveAttribute('aria-selected', 'true'); | |
| // 验证 Cronjob 列表表格可见 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The tests related to the namespace have been removed, is this the intended?
Additionally, can the tests related to statefulset be removed?
Oh I removed the namespace-related tests so that this PR only contains the cronjob-related tests, making it clearer. I will also remove the statefulset-related tests in this PR later. |
0a166f9 to
63f2ec5
Compare
|
@SunsetB612 is this PR ready to review, it seems that there still some common problems as daemonset/deplyment e2e test. |
b0d27a2 to
bedd380
Compare
| } | ||
| } | ||
| }, testCronJobYaml); | ||
| /* eslint-enable */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any better solution for duplicate code 🤔
| } | ||
| } | ||
| }, modifiedYaml); | ||
| /* eslint-enable */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ditto
|
@SunsetB612 for the problem of any, it must be corrected. for the problem of duplicate code, you can have a try to resolve the problem |
51eeb45 to
7ae82f2
Compare
|
|
||
| type ApiConstructor<T> = new (config: Configuration, ...args: any[]) => T; | ||
|
|
||
| // Set webServer.url and use.baseURL with the location of the WebServer |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not import it directly, like
import {ApiConstructor} from '@kubernetes/client-node';| export async function createK8sDeployment(yamlContent: string): Promise<void> { | ||
| try { | ||
| const k8sApi = createKarmadaApiClient(); | ||
| const k8sApi = createKarmadaApiClient(k8s.AppsV1Api); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Signed-off-by: SunsetB612 <[email protected]>
7ae82f2 to
36d70b0
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: warjiang The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
No description provided.