Open
Description
Rationale:
- less languages/frameworks to learn => easier start for contributors
- less languages/frameworks to support/maintain => less headache to me (CodeNarc and its plugin have issues: Generated CodeNarc report has unexpanded project version #508, Codenarc: find a way of providing codenarc.properties #539, codenarc fails on Windows with AssertionError: Invalid argument format: [Stamps] #994), less time I need to spend on this (for example, updating Gmaven plugin (Bump gmavenplus-plugin from 1.5 to 1.6.1 #958), Groovy ([Security] Bump groovy-all from 2.0.8 to 2.4.15 #938), Spock (Danger: highlight a failed spock test #761), CodeNarc (Update CodeNarc to 1.6.1 #1187), integration to our CI (CodeNarc is skipped on Travis CI when pom.xml was modified #1479))
- I noticed that tests on Spock/Groovy are running slower in IDEA than JUnit ones
- The community seems inactive so the future is unclear and features/updates get released longer
- JUnit has rich ecosystem
- I found that syntax sugar doesn't outweight all aforementioned
TODO:
- SlugUtilsTest
- LocaleUtilsTest
- PagerTest
- SeriesSalesServiceImplTest
- CatalogUtilsTest
- StampsCatalogServiceImplTest
- SeriesSalesImportServiceImplTest
- SeriesInfoExtractorServiceImplTest
- TimedSeriesInfoExtractorServiceTest
- SeriesImportServiceImplTest
- SeriesServiceImplTest
- CollectionServiceImplTest
- CategoryServiceImplTest
- ParticipantServiceImplTest
- FilesystemImagePersistenceStrategyTest
- ImageServiceImplTest
- TimedImagePreviewStrategyTest
- DatabaseImagePersistenceStrategyTest
- SiteServiceImplTest
- CronServiceImplTest
- SuspiciousActivityServiceImplTest
- UsersActivationServiceImplTest
- UserServiceImplTest
- CountryServiceImplTest
- Remove plugin, dependencies, build logic, Danger support, update editorconfig
- Close Groovy/Spock-related issues
- Update README/NEWS
- remove dependency on
junit-jupiter-engineand exclude (and ban?)junitfrom other dependencies - remove a comment for Danger: highlight a failed spock test #761