The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.This information is from the code coverage report (see http://coverage.cwgordon.com/coverage).
We need to test:
1) Auto-completing
2) Requesting a new password (can use mail.inc override to intercept the e-mail)
3) Editing a user (with malicious values and without)
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | issue-1214686.patch | 3.51 KB | lilou |
| #8 | user.test.patch | 3.46 KB | p.brouwers |
| #6 | user.test.patch | 3.46 KB | p.brouwers |
| #2 | user.test.patch | 3.22 KB | p.brouwers |
Comments
Comment #1
catchSplitting into three for the awesome testing party, so this only deals with #3 in the original list.
The other two tests are here:
#293487: TestingParty08: User password reset #293490: User autocomplete gives 403 errors with certain combinations of permissions
Comment #2
p.brouwers commentedI made some basic tests for "Editing a user (with malicious values and without)"
It can be expanded it bit more, but it's a start.
Comment #4
p.brouwers commentedComment #5
catchLooks like a good start. A few things though - getInfo() no longer has PHPdoc - see http://drupal.org/node/325974. Also a few comments in there should be formatted as full sentences with a space after the //. I'm also not sure about testing for the lack of
<div class="message"- any particular reason to do this rather than the specific text?Comment #6
p.brouwers commentedI made the adjustments as you suggested.
(hope I set the right Component)
Comment #8
p.brouwers commentedresubmitted patch, head was broken when test was run
Comment #10
lilou commentedNow,
t()is removed ingetinfo(): #500866: [META] remove t() from assert messageComment #12
catchMoving this out of the critical bugs queue - see #607038: Meta issue: fix gaps in code coverage.
Comment #13
jacob.embree commentedAll of these tests are present.