-
Notifications
You must be signed in to change notification settings - Fork 21
[O2B-1490] Add filtering by env ids to the environment filtering panel #2028
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
[O2B-1490] Add filtering by env ids to the environment filtering panel #2028
Conversation
Integrated the filtersPanelPopover component into the environment overview UI. Added a test to verify that the filtering panel can be successfully opened.
Adds FilteringModel to EnvironmentOverviewModel, enabling filter state management.
Introduces a raw text filter for environment IDs in the environments overview. Adds tests to verify filtering by single and multiple IDs.
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2028 +/- ##
==========================================
- Coverage 45.47% 45.45% -0.03%
==========================================
Files 1023 1023
Lines 17050 17051 +1
Branches 3092 3092
==========================================
- Hits 7754 7750 -4
- Misses 9296 9301 +5 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…-environment-filtering-panel
Removed the overridden getLoadParameters method from EnvironmentOverviewModel.
test/public/envs/overview.test.js
Outdated
| await fillInput(page, selector, inputValue, ['change']); | ||
| await waitForTableLength(page, expectedIds.length); | ||
| const table = await page.$$('tbody tr'); | ||
| expect(table.length).to.equal(expectedIds.length); |
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.
As far as I can tell, the waitForTableLength will already confirm the expected number of environments, so there is no need for this check.
I would even go further (as front-end tests tend to be quite slow), that the placeholder, we check it once at the start of the test, and then for each reset of filters, we do not recheck it to save just a bit of time.
Eliminated an unnecessary table length check that could slow down test speed.
Changed the filter input and expected results for a test case with filtering on env IDs. This is because test inputs following each other that result in the same number of rows in the table will cause incorrect functioning of the waitForTableLength whose job it is is to wait for the filter to be applied.
Introduces a raw text filter for environment IDs in the environments overview.
Adds tests to verify filtering by single and multiple IDs.
I have a JIRA ticket
Notable changes for users:
Notable changes for developers:
Changes made to the database: