-
Notifications
You must be signed in to change notification settings - Fork 528
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
fix: supports search by name for service options when add router. #2066
Conversation
TkClark
commented
Aug 12, 2021
•
edited
Loading
edited
- Web ui supports search by name for service options when add router.
- fix: When use the dashboard ui the priority of the route cann't be set if the upstream is not set when the route is set.
2. fixed the bug where the priority of the route cann't be set if the upstream is not set when the route is set.
✔️ Deploy Preview for apisix-dashboard ready! 🔨 Explore the source changes: 5e59e0a 🔍 Inspect the deploy log: https://app.netlify.com/sites/apisix-dashboard/deploys/6136e5f672b2b800088da576 😎 Browse the preview: https://deploy-preview-2066--apisix-dashboard.netlify.app/ |
Codecov Report
@@ Coverage Diff @@
## master #2066 +/- ##
==========================================
+ Coverage 67.48% 67.52% +0.04%
==========================================
Files 126 126
Lines 3294 3295 +1
Branches 802 802
==========================================
+ Hits 2223 2225 +2
+ Misses 1071 1070 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Hi @TkClark , would you please add test case for your bug fix? for example, create a Route with service and priority=1, and then check in the configure view to see if the priority field is 1 thanks very much. and I would be better to change your commit message to some thing like:
thanks very much. |
just fixed the frontend bugs. And i don't see the test of react frontend |
Thanks for your feedback @TkClark , then let's turn to the test cases. Here is our fe e2e test develop guide, hope this can help you to write and debug your test cases. Actually your pr contains two part of things: feat: supports search by name for service options when add routeryou can choose to start a new test file to add your test cases for this feature.
fix: would not set
|
it('should create route', function () { |
try to file in the
priority
field together with other fields.apisix-dashboard/web/cypress/integration/route/create-edit-duplicate-delete-route.spec.js
Line 210 in 98fe38a
it('should view the route', function () { |
try to check if the
priority
field existedapisix-dashboard/web/cypress/integration/route/create-edit-duplicate-delete-route.spec.js
Line 230 in 98fe38a
it('should edit the route', function () { |
try to check if the
priority
has the right value, you can refer this one cy.get({priority}).should('have.value', xxxx)
fix: would not set priority when create route add test cases for this feature.
OK. |
cy.contains('View').click(); | ||
cy.get(selector.drawer).should('be.visible'); | ||
cy.get(selector.monacoScroll).within(() => { | ||
cy.contains('priority').should('exist'); |
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.
LGTM
It would be better to check whether service_id
exist
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.
i was add check whether service_id exist for the test case
also cc @Baoyuantop @iamayushdas to have a look, thanks |
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.
LGMT
After checking the video log, we can found that the E2E failed caused by we need to find a better way to fix this unstable test case. video log here: |
re-run FE E2E test case |