2.5.13 The full Ruby and JavaScript test suites are taking some time to run
Related to the audit.
There are no issues with “too many tests”, but there could be an issue if these tests were slowing down the project development and releases.
It is to be said that most of this test time is due to Cucumber features tests, which take around 6 minutes to run. Switching to more vitest tests may help reduce this duration while keeping a good front-end testing behaviour, without being coupled to some Ruby code.
This switch could be made now, or after the front-end and back-end codes are split into two repositories.
In addition to this, we regularly reach the limit of free Gitlab CI pipelines minutes. I couldn't have the "opensource project status" for GardenParty, and sadly gave up after too many incomplete forms.
Recently, I started to write RSpec system tests instead of Cucumber's as I don't know if they really add value to the project, and it's quicker to write RSpec tests. Moving all the tests from Cucumber to RSpec won't help reducing the CI time, though.