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
When you only use the visualception modul for your tests and not tests from the codeception framework you have a lot of
$I->dontSeeVisualChanges('id', '#something');
After writing it the tenth time you ask for a configfile of ids and div container in a file you could read in.
I thing for some reasons it is easier to handle a configfile than write the dontSeeVisualChanges.
The text was updated successfully, but these errors were encountered:
Any ideas for the syntax?
$I->dontSeeVisualChangesByFile($configFileName); $I->dontSeeVisualChangesByArray($array); $I->dontSeeVisualChanges("Startpage"); VisualChange::dontSeeVisualChanges( $configFile, $I );
What would a config file look like?
Startpage: header: "#header" footer: "#footer" sub-navigation: ".subnav"
Sorry, something went wrong.
No branches or pull requests
When you only use the visualception modul for your tests and not tests from the codeception framework you have a lot of
$I->dontSeeVisualChanges('id', '#something');
After writing it the tenth time you ask for a configfile of ids and div container in a file you could read in.
I thing for some reasons it is easier to handle a configfile than write the dontSeeVisualChanges.
The text was updated successfully, but these errors were encountered: