7 commits

Author	SHA1	Message	Date
Paul Chavard	29bdd82b59	refactor(procedure): types_de_champ -> active_revision.types_de_champ_public	2022-11-17 13:54:14 +01:00
Martin	571452c530	bug(a11y.dropdown): la dropdown d'aide usager sur une procedure n'est pas a11y compatible	2022-11-08 16:40:17 +01:00
Martin	48b12d03f6	spec(wcag_usager_spec): add test on dropdown. broken 🤭	2022-11-08 16:40:17 +01:00
Martin	3f37102f97	spec(wcag_usager_spec): add test to dossiers_path with at least one dossier	2022-11-08 16:40:17 +01:00
Martin	0a4f17d245	chore(wcag_usager_spec): remove skips	2022-11-08 16:40:17 +01:00
Pierre de La Morinerie	970c3e4b2b	specs: avoid executing business logic in Procedure factory ... Calling business logic in a factory is a code-smell, because it usually requires the object to be saved into database, and may have unintended consequences when the business logic is changed. Also, this allows to just build a published procedure, without saving it to the database.	2021-11-23 08:07:07 +01:00
Pierre de La Morinerie	9fd38cae5e	specs: migrate from features to system specs ... System specs have been available since Rails 5.1, and are better integrated with the Rails framework. - Rename `spec/features` to `spec/system` - Rename `feature do` to `describe do` - Configure Capybara for system specs Steps mostly taken from https://medium.com/table-xi/a-quick-guide-to-rails-system-tests-in-rspec-b6e9e8a8b5f6	2021-10-26 12:24:46 +02:00