garris / garris/BackstopJS

Having issue with slimerjs. i.e Can't able to run with engine=slimerjs.

Open
#242 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
7.2k
Forks
621
PR merge metrics
No merged PRs in 30d

Description

I am able to run this framework properly with engine=phantomjs. which is mentioned in backstop.json.
but can't able to run with engine=slimerjs.

Small window gets open and closed immediately. I am following same steps as mentioned in Readme document.

I am trying this on windows 7.
and from node js or command prompt i am executing command from directory i.e "Backstop/node_modules/backstopjs " like "npm run reference" and "npm run test".

Nothing has happened.No Reference directory has created.

Could you please have any workaround or suggestion.

command logs shows

C:\Phantom\BackstopJs\node_modules\backstopjs>npm run reference

> backstopjs@1.3.5 reference C:\Phantom\BackstopJs\node_modules\backstopjs
> gulp reference

BackstopJS Config loaded at location C:\Phantom\BackstopJs\backstop.json
[15:08:18] Using gulpfile C:\Phantom\BackstopJs\node_modules\backstopjs\gulpfile.js
[15:08:18] Starting 'clean'...
bitmaps_reference was cleaned.
[15:08:18] Starting 'bless'...
[15:08:18] Finished 'bless' after 3.83 ms
[15:08:18] Finished 'clean' after 12 ms
[15:08:18] Starting 'reference'...
gulp.run() has been deprecated. Use task dependencies or gulp.watch task triggering instead.
[15:08:18] Starting 'init'...
[15:08:18] Finished 'init' after 4.45 μs
[15:08:18] Starting 'test'...

Generating reference files.

Running CasperJS with: [ 'capture/genBitmaps.js', '--engine=slimerjs' ]
[15:08:18] Finished 'test' after 11 ms
reference has run.
[15:08:18] Finished 'reference' after 14 ms

Bitmap file generation completed.

Run `$ npm run test` to generate diff report.

Contributor guide

Open the contributing guide

Research direction

Start by comparing the SlimerJS setup in the README and backstop.json with the command output. Then inspect gulpfile.js and capture/genBitmaps.js around the engine invocation, and reproduce the reference command on the reported Windows setup. Done means the SlimerJS path either completes reference generation or reports a clear, actionable failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.