Replace Jest with Jasmine Javascript Testing Framework to the Project

[FireLemons]

Description

Jest cannot to my knowledge access any of the html generated by rails. Jasmine can wrap a rails page and run and display tests on it which allows selenium to read the output. It can also mock javascript time.

• [ ] Install Jasmine
• [ ] Configure Jasmine to only turn on when running tests
• [ ] Replace the jest tests with jasmine tests
• [ ] Remove jest

Screenshots of Jasmine

How to access the QA site

Login Details:
Link to QA site

Login Emails:

• volunteer1@example.com view site as a volunteer
• supervisor1@example.com view site as a supervisor
• casa_admin1@example.com view site as an admin
• all_casa_admin1@example.com view site as an all casa admin
  • go to /all_casa_admins/sign_in

password for all users: 12345678

Questions? Join Slack!

We highly recommend that you join us in slack https://rubyforgood.herokuapp.com/ #casa channel to ask questions quickly and hear about office hours (currently Tuesday 5-7pm Pacific), stakeholder news, and upcoming new issues.

[Nwabor]

I can work on this..

[FireLemons]

Sorry someone else is already working on this.

[littleforest]

@FireLemons is there really a need for a separate JavaScript testing framework? Is there any reason why we can't just test JS behavior through the system specs?

[FireLemons]

There's no way to mock timeouts / intervals

[github-actions[bot]]

This issue has been inactive for 261 hours (10.88 days) and will be unassigned after 99 more hours (4.13 days). If you have questions, please

If you are still working on this, comment here to tell the bot to give you more time

[github-actions[bot]]

This issue has been inactive for 381 hours (15.88 days) and is past the limit of 360 hours (15.00 days) so is being unassigned.You’ve just been unassigned from this ticket due to inactivity – but feel free to pick it back up (or a new one!) in the future! Thank you again for your contribution to this project.

[seanmarcia]

This feels like a bad idea. I'd really like to understand the problem this is solving before making major framework changes. This has the same feel to me as when Cypress was implemented and then we later needed to pull it out.

[github-actions[bot]]

This issue has been open without changes for a long time! What's up?

[compwron]

I am closing this as old. We may bring it back in a different form.