Skip to content
New issue

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

Swap jasmine gem for new runner #382

Merged
merged 2 commits into from
Jan 15, 2025
Merged

Conversation

tombye
Copy link
Contributor

@tombye tombye commented Jan 15, 2025

What’s changed

The way we run the JS tests currently relies on 2 defunct technologies:

  • the jasmine-gem ruby gem
  • phantomjs

This swaps them out for the jasmine-browser-runner npm package to manage the jasmine part and google chrome to run them.

Identifying a user need

A recent pull request's tests failed when building phantomjs on the latest ubuntu. I don't know enough about C to diagnose the exact cause but no one is maintaining phantomjs so any fixes are unlikely.

This doesn't meet a need in itself but any pull requests that do can't currently be merged and this should unblock that.

The Jasmine ruby gem is deprecated:

https://github.com/jasmine/jasmine-gem?tab=readme-ov-file#discontinued

PhantomJS, the headless webkit browser used by the
Jasmine gem, is no longer being worked on:

https://phantomjs.org/

This follows the guidance in the Jasmine docs and
replaces the gem and phantomJS with the
jasmine-browser-runner npm package.

Because the new setup isn't in ruby, dependencies
'required' in JS files now need to be included
manually in the config.
@tombye tombye changed the title [DO NOT MERGE] Swap jasmine gem for new runner Swap jasmine gem for new runner Jan 15, 2025
@tombye tombye changed the title Swap jasmine gem for new runner [DO NOT MERGE] Swap jasmine gem for new runner Jan 15, 2025
@tombye tombye force-pushed the swap-jasmine-gem-for-new-runner branch from 0faed4c to a963cd0 Compare January 15, 2025 15:22
We don't get a jasmine rake task so need
to create one in the Rakefile.
@tombye tombye force-pushed the swap-jasmine-gem-for-new-runner branch from a963cd0 to 87a5284 Compare January 15, 2025 15:25
@tombye tombye changed the title [DO NOT MERGE] Swap jasmine gem for new runner Swap jasmine gem for new runner Jan 15, 2025
Copy link
Contributor

@marcotranchino marcotranchino left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@tombye tombye merged commit e65e6d0 into main Jan 15, 2025
3 checks passed
@tombye tombye deleted the swap-jasmine-gem-for-new-runner branch January 15, 2025 15:53
@tombye tombye mentioned this pull request Jan 15, 2025
tombye added a commit that referenced this pull request Jan 16, 2025
This was missed from the pull request that
replaced the jasmine ruby gem with the
jasmine-browser-runner:

#382
tombye added a commit that referenced this pull request Jan 16, 2025
This was missed from the pull request that
replaced the jasmine ruby gem with the
jasmine-browser-runner:

#382
tombye added a commit that referenced this pull request Jan 16, 2025
This was missed from the pull request that
replaced the jasmine ruby gem with the
jasmine-browser-runner:

#382
tombye added a commit that referenced this pull request Jan 16, 2025
This was missed from the pull request that
replaced the jasmine ruby gem with the
jasmine-browser-runner:

#382
tombye added a commit that referenced this pull request Jan 16, 2025
This was missed from the pull request that
replaced the jasmine ruby gem with the
jasmine-browser-runner:

#382
tombye added a commit that referenced this pull request Jan 16, 2025
This was missed from the pull request that
replaced the jasmine ruby gem with the
jasmine-browser-runner:

#382
tombye added a commit that referenced this pull request Jan 17, 2025
This was missed from the pull request that
replaced the jasmine ruby gem with the
jasmine-browser-runner:

#382
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants