Commit 4a983205 authored by Mark Florian's avatar Mark Florian

Fix skipped spec

parent 291c2937
...@@ -504,29 +504,22 @@ describe('MrWidgetOptions', () => { ...@@ -504,29 +504,22 @@ describe('MrWidgetOptions', () => {
}); });
describe('rendering relatedLinks', () => { describe('rendering relatedLinks', () => {
beforeEach((done) => { beforeEach(() => {
wrapper.vm.mr.relatedLinks = { createComponent({
assignToMe: null, ...mockData,
closing: ` issues_links: {
<a class="close-related-link" href="#"> closing: `
Close <a class="close-related-link" href="#">
</a> Close
`, </a>
mentioned: '', `,
}; },
nextTick(done); });
return nextTick();
}); });
// This test was previously written using the toBeDefined() matcher. In it('renders if there are relatedLinks', () => {
// migrating this suite to @vue/test-utils, the matcher had to be
// changed, which causes this test to fail. This is because the
// toBeDefined() matcher was was incorrectly passing before: it checks
// that the result is not `undefined`, and since `querySelector` can only
// return `null` or an `HTMLElement`, it could never fail. So, at some
// point, the expected behavior was broken or removed in the
// implementation.
// eslint-disable-next-line jest/no-disabled-tests
it.skip('renders if there are relatedLinks', () => {
expect(wrapper.find('.close-related-link').exists()).toBe(true); expect(wrapper.find('.close-related-link').exists()).toBe(true);
}); });
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment