The help text which run-tests.sh outputs contains an example of how to invoke the script without a working database or settings.php

$ php core/scripts/run-tests.sh | tail -n8
Without a preinstalled Drupal site and enabled Simpletest module, specify a
SQLite database pathname to create and the default database connection info to
use in tests:

sudo -u [wwwrun|www-data|etc] php ./core/scripts/run-tests.sh
  --sqlite /tmpfs/drupal/test.sqlite
  --dburl mysql://username:password@localhost/database
  --url http://example.com/ --all

However, it could be made a little clearer that the sqlite db here is for the test runner, and the mysql db is for Drupal.

CommentFileSizeAuthor
#4 2890023-run-tests-script-clarify-dburl-4.patch703 bytesmcdruid
#2 2890023-run-tests-script-wrong-dburl-2.patch486 bytesmcdruid

Issue fork drupal-2890023

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

mcdruid created an issue. See original summary.

mcdruid’s picture

mcdruid commented
Status: Active » Needs review
StatusFileSize
new 2890023-run-tests-script-wrong-dburl-2.patch486 bytes
ricardoamaro’s picture

ricardoamaro commented

This is what we used to have:

# --dburl is the effective database connection that is being used for all tests. Can be any database driver supported by core
# --sqlite database is used for the test runner only (and only contains the simpletest module database schema)
#Example: php ./core/scripts/run-tests.sh --sqlite /tmpfs/drupal/test.sqlite --dburl mysql://username:password@localhost/database --url http://example.com/ --all

mcdruid’s picture

mcdruid commented
Title: run-tests.sh example command has wrong type of --dburl » clarify db settings for run-tests.sh example command
StatusFileSize
new 2890023-run-tests-script-clarify-dburl-4.patch703 bytes

Thanks Ricardo. I think I misunderstood what the example illustrates - it is possible to use sqlite as Drupal's db (as well as for the test runner), but that's not a very typical configuration (and it looks like it's not unusual for several tests to fail with sqlite as the db).

Here's a new patch which reverts the change (dburl back to mysql) and adds a few extra words to the explanation of the example to clarify the purpose of the two different database settings.

mcdruid’s picture

mcdruid commented
mcdruid’s picture

mcdruid commented
Issue summary: View changes

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

joachim’s picture

joachim commented
Status: Needs review » Needs work 
+++ b/core/scripts/run-tests.sh
@@ -325,8 +325,8 @@ function simpletest_script_help() {
+SQLite database pathname to create (for the test runner) and the default
+database connection info (for Drupal) to use in tests:

I don't really understand either the old or the new wording in this patch, because in the example command below, there is only one database argument, but the text talks about two things.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Issue tags: +DX (Developer Experience)
Related issues: +#1808220: Remove run-tests.sh dependency on existing/installed parent site

#1808220: Remove run-tests.sh dependency on existing/installed parent site introduced this.

quietone made their first commit to this issue’s fork.

quietone opened merge request !8853

quietone’s picture

quietone commented
Status: Needs work » Needs review

Made an MR from the latest patch. The text reads well to me. I am not sure what @joachim saw, but the example after this text has used both the --sqlite and --dburl parameters since 2014.

needs-review-queue-bot’s picture

needs-review-queue-bot commented
Status: Needs review » Needs work

The Needs Review Queue Bot tested this issue.

While you are making the above changes, we recommend that you convert this patch to a merge request. Merge requests are preferred over patches. Be sure to hide the old patch files as well. (Converting an issue to a merge request without other contributions to the issue will not receive credit.)

quietone’s picture

quietone commented
Status: Needs work » Needs review
Issue tags: +no-needs-review-bot
smustgrave’s picture

smustgrave commented
Status: Needs review » Reviewed & tested by the community

Also agree update reads fine, see no issue.

  • nod_ committed 4c3ce18a on 11.x 
    Issue #2890023 by mcdruid, quietone, ricardoamaro: clarify db settings...

nod_ closed merge request !8853

nod_’s picture

nod_
Primary language French
Location Lille
commented
Status: Reviewed & tested by the community » Fixed

Committed 4c3ce18 and pushed to 11.x. Thanks!

Status: Fixed » Closed (fixed)

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