Closed (fixed)
Project:
Protected Forms
Version:
2.0.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
10 Feb 2023 at 07:10 UTC
Updated:
16 Jul 2025 at 13:59 UTC
Jump to comment: Most recent
Currently, only a few tests exist, which don't cover all the complex functionality of this module.
To be sure, everything works as expected, especially
with combinations, single words, phrases etc.
Furthermore install and uninstall without errors should be checked and we should ensure the schema is correct, e.g. using config_inspector.
This is something the community (us!) can do, if the maintainer doesn't have the time.
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
anybodyComment #3
altagrade commentedUnfortunately, no time for writing tests. Mind becoming a co-maintainer?
Comment #4
anybodyThank you, @AltaGrade, well if you'd like to, we can help. In that case also please add @Grevil as Co-Maintainer and I'll add these task to our companies TODO-list. Nice and helpful module, thanks :)
Comment #5
altagrade commentedThanks for agreeing to co-maintain this module. I've just given you all maintainer privileges, including the "Administer maintainers", so please go ahead and add @Grevil or whomever you deem necessary to add.
We have developed and do keep maintained this module mainly for our Backdrop customer project. Because of Backdrop and Drupal 7 similarities the changes made on Backdrop are easy to quickly pass to Drupal 7.
However, unfortunately Drupal 9/10 version is many features behind. So we do hope you can move all the new features from either Backdrop or Drupal 7 to Drupal 9/10.
Comment #6
anybodyThank you, I just created a separate issue for that: #3341697: Implement Backdrop / Drupal 7 features for 2.x
I don't think we'll have the time short-term, but I'll add this to our list.
Comment #7
anybodyComment #8
anybody@Grevil will have a look when we have the time! :)
Comment #9
anybodyMoved schema fixes to #3436411: Fix schema and add generic functional test
Comment #10
anybodyhttps://www.drupal.org/project/crowdsec is an alternative now.
Comment #11
lrwebks commentedWhat tests are left to do after the merge of #3348032: Colon identified as a spam character:
Regarding the other things mentioned in the issue summary: Install / uninstall tests are already covered by
ProtectedFormsGenericTest.php, but I will take a look at the schema manually via Config Inspector.Comment #13
anybodyComment #14
anybodyComment #15
lrwebks commentedAll three tests are added now, however the last one isn't fully working yet since I struggle to find the correct permission name for a user to access the DBLog page. @anybody are you in the know?
Comment #16
lrwebks commentedComment #17
anybodyIt's simply not a good idea to give anonymous users all these permissions. Would be better to use an authenticated user.
But let's stop here, enough time went in. I think this is a good one for @Grevil to review and teach you a bit in testing, if he finds possible improvements.
Nice work :)
Comment #18
lrwebks commentedFixed the test, everything should be working now.
Comment #19
anybodyComment #20
grevil commentedAdded a few comments. I understand that much of the code I commented was simply copied and pasted from the existing test, please also adjust it there. Furthermore, many of my critics given also apply to the other tests.
The core of the tests are great! Well done! :)
Comment #21
lrwebks commentedThe tests are alright now! I have added “whitelisted” to the CSpell project words, since it is part of a reject pattern and also used a lot in the tests (I think we don't need to open a separate issue just for that and the pipeline is entirely green now).
Comment #22
lrwebks commentedNeed to remove "whitelisted" from project words again since apparently Drupal Core flags it directly via cspell...
Comment #23
lrwebks commentedComment #24
anybodyNice work @lrwebks thank you!
Comment #26
anybody