-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Code] fix history functional test #37332
[Code] fix history functional test #37332
Conversation
💔 Build Failed |
💔 Build Failed |
💚 Build Succeeded |
retest |
💚 Build Succeeded |
retest |
💚 Build Succeeded |
retest |
💔 Build Failed |
retest |
💔 Build Failed |
💔 Build Failed |
💚 Build Succeeded |
retest |
const tabText = await (await find.byCssSelector('.euiTab-isSelected')).getVisibleText(); | ||
expect(tabText).to.equal('Structure'); | ||
// if structure tree tab is active, file tree tab's `data-test-subj` would be `codeFileTreeTab` | ||
expect(testSubjects.exists('codeFileTreeTab')).to.be.ok(); |
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.
should we change to codeStructureTreeTabActive
which is more readable?
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.
change to codeStructureTreeTabActive
would affect explore_repository
test, can we leave it for now
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.
ok
💔 Build Failed |
retest |
💔 Build Failed |
💚 Build Succeeded |
can we try to rerun this test with it enabled multiple times to make sure it won't be flaky? |
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.
see my comments above
It ran hundreds of times before, and the results were good(some failures were caused by other tests) |
retest |
💚 Build Succeeded |
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.
Let's just leave this PR in master, without backporting them to 7.x or 7.2
// expect(await testSubjects.exists('codeSourceViewer')).to.be(true); | ||
// }); | ||
// }); | ||
it('Click file/directory on the right panel', async () => { |
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 think in this PR, the explore-repository test is skipped, so do we need to keep the changes in this file?
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.
Let's keep the change since we are gonna uncomment this any way
|
* enable history functional test and fix flaky test
Summary
Summarize your PR. If it involves visual changes include a screenshot or gif.
Checklist
Use
strikethroughsto remove checklist items you don't feel are applicable to this PR.For maintainers