Fixed my own issue.

I created a computed property - isDesktop() - that returns “this.$q.platform.is.desktop”. Then within my test file, I dynamically updated the computed property that then allowed me to test the functionality.

I defined a factory function that is then called in beforeEach().

const factory = (computed = { }) => {
return shallowMount(App, {
computed
});
};

beforeEach(() => {
wrapper = factory();
});

For the test that requires the updated computer property, I then called the factory function and set the computed property value.

it(‘my amazing test’, () => {
wrapper = factory({
isDesktop: () => false
});

expect(addYourAssertionHere)
})

@nothingismagick You guys are doing such an awesome job addressing all the issues cropping up. I can imagine you’re working your butts off. It’s very much appreciated.

@nothingismagick thank you for your help. I suspect I must have had case-matching turned on during the search for that line of code, so apologies for the silly question.

I would be happy to forego console.log() and begin using the Chrome debugger but I have been unable to get this to work with Quasar. I have tried the following:

Add debugger statement to the test code Run the tests using yarn test:unit:debug Navigate to ‘chrome://inspect’ Click on the ‘inspect’ link for Remote Target: jest file:///

New Chrome window opens with:

Uncaught Error: Cannot find module '<my-project-folder>\jest'

A guide to accessing debugging would be a great addition to the Quasar Testing documentation. 🙂

could you please tell me how to test the opening and closing of the dialog ?