Make continuous deployment safe by comparing before and after webpage screenshots for each release. Depicted shows when any visual, perceptual differences are found. This is the ultimate, automated end-to-end test.
This logs stack traces when there are JS errors in the capture log. Previously it would log "[Object object]" for every function in the stack.
This also prints out the path to every log file generated by local dpxdt. Previously these were only visible if you ran with --verbose, at which point they were buried in stack traces and other messages. They're essential for debugging, and this puts them front and center.
This logs stack traces when there are JS errors in the capture log. Previously it would log "[Object object]" for every function in the stack.
This also prints out the path to every log file generated by local dpxdt. Previously these were only visible if you ran with
--verbose
, at which point they were buried in stack traces and other messages. They're essential for debugging, and this puts them front and center.Fixes #110