Releases: garris/BackstopJS
enhancement: ignoreAntialiasing
-
Add option to use resemble`s ignoreAntialiasing() (#629)
-
updated docs
Some long awaited contributions from the community.
@lsuchanek -- Enabled change of starting port in configuration. e.g. "startingPort": 9333
@kiran-redhat -- Upgrade chromy from 0.5.5 to 0.5.7 (#615)
@Baltazardoung -- Tagging docker images (#617)
@anton-kulagin -- update junit report creating and prevent caching outdated test results (#619)
@deap82 -- Access to static Chromy functions (#621)
@trungdq88 -- logging user config if detected in options
(when debug = true)
Thank you everyone for your contributions!
This update has been pushed to NPM.
add engineOptions to config
Enables setting/overriding of Chromy options. See docs for more detail... https://github.com/garris/BackstopJS#setting-chromy-option-flags
Please note:
- Setting
port
is way not advised. - Setting
--window-size
will override values used in your viewport settings.
fixes hanging error on chromy exception
fixes 549 — hanging error on chromy exception
- tests failing because of a chromy error exception (not backstop error) now resolve with an error instead of bubbling up a rejection.
- incomplete test data is decorated with exception data and added to testPairs
- Chromy.cleanup is called when all chromy instances have settled
- comparison flow now guards against incomplete test data
- Comparison flow now handles TEST RUN EXCEPTIONS
- cleaned up cli report
BACKSTOP 3 with chrome-headless support
BackstopJS 3
Supports screen rendering with Chrome-headless, Phantom and SlimerJS.
Supports interaction testing with ChromyJS and CasperJS scripting.
Also OBEY THE LEMUR!
Fixes setting cookies with onBeforeScript
See /examples/set cookies onBefore/
Setting cookies with onBeforeScripts now works.
Many thanks to @shanemcgraw for this fix!
Concurrency support
Now you are able to tun Multiple concurrent BackstopJS instances...
Issue described in here: #363
Also added:
--testReportFileName parameter is added for customized xunit filenames
e.g.
backstop test --testReportFileName=<customReportName>
Many thanks to uğur mirza zeyrek!
Command line args: --filter, --user, --password
--filter=<scenario.name> arg now expects regex strings (comma separated values still supported)
--user= now passes this through to casper arguments
--password= now passes this through to casper arguments
BackstopJS image comparison performance
During a test, BackstopJS processes image comparisons in parallel. By default, this value is limited to 50. Used this way, BackstopJS can utilize available processor power while keeping RAM usage under control.
This value can be adjusted as needed to increase/decrease the amount of RAM required during a test.
As a (very approximate) rule of thumb, BackstopJS will use 100MB RAM plus approximately 5 MB for each concurrent image comparison.
To adjust this value add an asyncCompareLimit
property to the root of your config like so...
"asyncCompareLimit": 100
// Would require 600MB to run tests.