Problem/Motivation
When someone submits patches to this module, there is no way for the maintainers to tell if that patch introduces a regression.
Proposed resolution
Add automated tests.
Remaining tasks
- Write a patch
- Maintainer set up automated testing for issues
- Review and feedback
- RTBC and feedback
- Commit
User interface changes
None.
API changes
None.
Data model changes
None.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | 3192574-5--add-tests.patch.patch | 15.55 KB | szhu |
Comments
Comment #2
szhu commentedHere is an initial patch, I still have more tests to add so don't commit, please :)
Comment #3
szhu commentedHere is an updated patch, I need to clean it up, I am just posting my progress thus far.
Comment #4
szhu commentedUpdated duplicated node test.
Comment #5
szhu commentedReady for final review.
Comment #6
szhu commentedComment #7
geoanders commentedTesting /var/www/html/web/anti_duplicates
SSSSSS 6 / 6 (100%)Time: 03:06.108, Memory: 6.00 MB
OK, but incomplete, skipped, or risky tests!
Tests: 6, Assertions: 6, Skipped: 6.
Remaining self deprecation notices (5)
3x: Declaring ::setUp without a void return typehint in Drupal\Tests\anti_duplicates\FunctionalJavascript\GlobalConfigurationTest is deprecated in drupal:9.0.0. Typehinting will be required before drupal:10.0.0. See https://www.drupal.org/node/3114724
3x in DrupalListener::startTest from Drupal\Tests\Listeners
2x: Declaring ::setUp without a void return typehint in Drupal\Tests\anti_duplicates\FunctionalJavascript\DetectDuplicateNodeTest is deprecated in drupal:9.0.0. Typehinting will be required before drupal:10.0.0. See https://www.drupal.org/node/3114724
2x in DrupalListener::startTest from Drupal\Tests\Listeners
Comment #9
geoanders commentedSeems to be working on latest branch. All tests have passed. Setup on project to run weekly.
Comment #10
geoanders commented