Use .trigger(‘click’) instead of .click
This is to improve reliability on mentioned tests
This commit is contained in:
parent
e7e132529b
commit
65c2f43fd3
2 changed files with 2 additions and 2 deletions
|
@ -158,7 +158,7 @@ describe 'Issue Boards', feature: true, js: true do
|
||||||
end
|
end
|
||||||
|
|
||||||
page.within(first('.board')) do
|
page.within(first('.board')) do
|
||||||
find('.card:nth-child(2)').click
|
find('.card:nth-child(2)').trigger('click')
|
||||||
end
|
end
|
||||||
|
|
||||||
page.within('.assignee') do
|
page.within('.assignee') do
|
||||||
|
|
|
@ -43,7 +43,7 @@ describe 'Dashboard > milestone filter', feature: true, js: true do
|
||||||
end
|
end
|
||||||
|
|
||||||
it 'should not change active Milestone unless clicked' do
|
it 'should not change active Milestone unless clicked' do
|
||||||
find(milestone_select).click
|
find(milestone_select).trigger('click')
|
||||||
|
|
||||||
expect(find('.dropdown-content')).to have_selector('a.is-active', count: 1)
|
expect(find('.dropdown-content')).to have_selector('a.is-active', count: 1)
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue