Timeline for Faster phpunit-bootstraping for single Unit-Tests
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2022 at 6:00 | history | tweeted | twitter.com/StackDrupal/status/1537676423808356352 | ||
| Jun 16, 2022 at 21:19 | history | became hot network question | |||
| Jun 16, 2022 at 14:44 | vote | accept | mullzk | ||
| Jun 16, 2022 at 14:44 | history | edited | mullzk | CC BY-SA 4.0 |
Update after Feedback from Kevin, the issue is not in Drupal and bootstrap.php, but in Vagrant and Virtualbox
|
| Jun 16, 2022 at 13:23 | answer | added | Kevin | timeline score: 3 | |
| Jun 16, 2022 at 13:18 | comment | added | Kevin | This sounds wrong. Unit tests execute very quickly as its only running raw code, there is no full Drupal bootstrap like Kernel or Functional tests. I can run 100 unit tests on my projects in a few seconds or less. phpunit can take arguments of which types of tests to run. Make sure your <testsuites> directive in phpunit.xml is set only to the path(s) of your custom module folder. | |
| S Jun 16, 2022 at 13:16 | review | First questions | |||
| Jun 16, 2022 at 13:22 | |||||
| S Jun 16, 2022 at 13:16 | history | asked | mullzk | CC BY-SA 4.0 |