This is a simple test case to ensure that the regcode settings form may be accessed only by users with the correct permissions. This is meant to be a first test case to provide the code framework and an example for future tests.

CommentFileSizeAuthor
#2 3225738-2-functional-test.patch2.3 KBtr

Issue fork regcode-3225738

Command icon Show commands

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:

About issue forks

Comments

TR created an issue. See original summary.

tr’s picture

tr commented
Status: Active » Needs review
StatusFileSize
new 3225738-2-functional-test.patch2.3 KB

Status: Needs review » Needs work

The last submitted patch, 2: 3225738-2-functional-test.patch, failed testing. View results

tr’s picture

tr commented

Very interesting. The test works fine on my local system, but fails on DrupalCI. This seems to be due to the encoding on the database, and is the exact problem pointed out in #3057418: SQLSTATE[42000]: Syntax error or access violation. Evidently we need to finish fixing that other issue in order for regcode tests to work on DrupalCI.

tr’s picture

tr commented
Version: 8.x-1.x-dev » 2.0.x-dev
tr’s picture

tr commented
Status: Needs work » Active

Moved to 2.0.x and opened an MR for testing on GitLab CI.

TR opened merge request !10

tr’s picture

tr commented
Status: Active » Fixed

Well the patch from #2 works on GitLab CI running Drupal 10 or Drupal 11. That's good enough for me.

#3057418: SQLSTATE[42000]: Syntax error or access violation is still an issue, but it least it doesn't have to block this too.

  • TR committed ffcdfa24 on 2.0.x 
    Issue #3225738 by TR: Add test case for settings form

  • TR committed a0b6f039 on 8.x-1.x 
    Issue #3225738 by TR: Add test case for settings form
tr’s picture

tr commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.