We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I tried to set screenshot size with width 360px or 414px but it is impossible and for these cases Chrome set width to 500px.
my config: config.services = [ [ 'novus-visual-regression', { compare: new VisualRegressionCompare.Spectre({ url: testEnv.spectreUrl, project: 'WEB', suite: 'Visual regression testing', test: function getTest(context) { return context.test.title; }, browser: function getBrowser(context) { return context.browser.name; }, size: function getSize(context) { return context.meta.viewport.width; }, fuzzLevel: 30 }), viewportChangePause: 3000, viewports: [ { width: 360, height: 640 }, { width: 414, height: 736 }, { width: 640, height: 480 } ], } ] ];
Is it possible to make screenshots with a width less than 500px, maybe some workarounds?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I tried to set screenshot size with width 360px or 414px but it is impossible and for these cases Chrome set width to 500px.
my config:
config.services = [
[
'novus-visual-regression',
{
compare: new VisualRegressionCompare.Spectre({
url: testEnv.spectreUrl,
project: 'WEB',
suite: 'Visual regression testing',
test: function getTest(context) {
return context.test.title;
},
browser: function getBrowser(context) {
return context.browser.name;
},
size: function getSize(context) {
return context.meta.viewport.width;
},
fuzzLevel: 30
}),
viewportChangePause: 3000,
viewports: [
{ width: 360, height: 640 },
{ width: 414, height: 736 },
{ width: 640, height: 480 }
],
}
]
];
Is it possible to make screenshots with a width less than 500px, maybe some workarounds?
The text was updated successfully, but these errors were encountered: