I'm following the readme instructions and reach the ddev drupal install phase.

$ ddev drupal install


 Select an installation profile [Install with commonly used features pre-configured.]:
  [standard  ] Install with commonly used features pre-configured.
  [minimal   ] Build a custom site without pre-configured functionality. Suitable for advanced users.
  [demo_umami] Install an example site that shows off some of Drupal’s capabilities.
 >

17/17 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓]
Congratulations, you installed Drupal!
Username: admin
Password: <password>

then I run echo 'show tables' |ddev mysql and nothing is shown, indicating that the DB is in fact empty.

Is there a reason you picked the seleniarm/standalone-chromium image? Performance on OSX?

I'm using the official drupalci packages, so you have the same as on DrupalCI/GitlabCI test runs: drupalci/webdriver-chromedriver:production.

I tried adding an xDebug breakpoint in a phpunit test and then ran ddev phpunit /path/to/test.php and it blew right past that spot. Is it possible to debug tests in this way?

If Drupal is installed using the recommended project composer template, then the core directory is in /var/www/html/web/ rather than /var/www/html/. This breaks the paths in this addon placing phpunit.xml

Would it be possible to attempt to detect the existence of the core directory before attempting to copy/alter files into that directory?

Please consider adding a ddev-get topic to the repo.

This will allow others to find this addon by using: ddev get --list --all

Steps

1. Click the "cogs" icon
   

2. Add ddev-get as a topic.
   

3. Run ddev get --list --all and check if this repo appears (should appear within a minute).