The module should have test coverage; it increases confidence in development.
- https://www.drupal.org/docs/develop/automated-testing β
Visit the following URLs and see no recent automated testing
- https://git.drupalcode.org/project/flysystem/-/pipelines
-
https://www.drupal.org/node/2489154/qa β
1. Identify some testing outcomes which feel readily achievable
2. Implement
3. Configure project for Gitlab CI
1. Identify some testing outcomes which feel readily achievable
2. Implement
3. Configure project for Gitlab CI
None
None identified or proposed
None identified or proposed
Active
3.0
Code
It would be great if this can happen as part of π± Planning for Release 3.0.0, Drupal 10.3+ Compatibility, Flysystem v3.1 Compatibility Needs work , setting that as parent issue.