This information is from the code coverage report (see http://coverage.cwgordon.com/coverage).

We need to test:

1) Viewing aggregator/categories/* pages. Addresses by post 52
2) Appropriate aggregator feeds periodically refreshing. Currently working in D8 module (AggregatorCronTest.php)
3) The aggregator module's provided blocks. Currently working in D8 module (AggregatorRenderingTest.php)
4) aggregator_element_data().
5) aggregator_refresh() with specified etag and modified.
6) Update with no new syndicated content.
7) Update to a moved feed.
8) Make sure lines 607-609 use theme('image') instead of other stupid stuff.
9) Update to unparsable feeds.
10) aggregator_parse_w3cdtf()
11) Trying to use aggregator_parse_feed() to parse invalid xml.
12) Update a feed with more than one new item.
13) Attempt to update to a feed with a duplicate item.
14) Update to a feed in a category.
15) View feed items in a category.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Berdir’s picture

Component: tests » aggregator.module
Status: Active » Needs review
FileSize
7.43 KB

Ok, attached is a first version of updated tests.

Note: Currently, the categorize tests *will* fail, this is because of : #423690: menu_link_maintain(), $op update critically broken.

Contained tests:
- Feed and Category blocks (checks existence, activating, title and feed items)
- Category page, including title and feed items check
- Update a category (this will "fail")
- Delete a category

Untouched functions :
- aggregator_cron (I have to figure out what that actually does)
- aggregator_sanitize_configuration: Will do that later
- aggregator_block_configure/aggregator_block_save- Need to test the block settings

I cheated (many stuff of the file has been moved to other files), but aggregator.module is now at 85% code coverage, which is a start :)
modules/aggregator/aggregator.module 387 65 85.62%

This not finished, but I'm setting it to review so that the tests can run.

Status: Needs review » Needs work

The last submitted patch failed testing.

Berdir’s picture

Status: Needs work » Needs review
FileSize
11.12 KB
23.99 KB

Some more tests.

Note: I've found another bug that needs to be fixed to get these tests to pass. This one is in aggregator.module, but I created a new issue so that it can easily be fixed while the tests can be improved. See #423886: aggregator_block_save fails with "Field 'description' doesn't have a default value". This patch will have multiple fails because of that bug.

With the latest patch, code coverage is now at 95% and aggregator.test has 805 test assertions.

I still need to add some apidocs and probably inline docs to some stuff.

The last submitted patch failed testing.

webchick’s picture

alex_b’s picture

#293318: Convert Aggregator feeds into entities contains a test module and tests for fetcher, parser and processor plugins.

I see that you're testing another aspect of the pluggable architecture though: the sanitize() function. So, right now, there is no overlap.

If ever such tests should be part of this patch though, it would be great if you could copy them from there - this would make my job of keeping 293318 up to date muuuch easier.

Need to run now, will review patch later in more detail.

Dries’s picture

I'm delegating this patch to alex_b because his work on aggregator module. I will commit this patch (after a quick review) when alex_b thinks this patch is ready. Thanks!

Berdir’s picture

@alex_b: I tried to focus on testing functions inside the file aggregator.module. That mainly includes hooks (especially block), api functions and also the sanitize function.

Berdir’s picture

aggregator.module has changed a lot since the initial list was made, but of that list, the following things are tested in this issue:

1) Viewing aggregator/categories/* pages.
Loading one category page and checking the page title (category name) and the feed item titles.

2) Appropriate aggregator feeds periodically refreshing.
Is that referencing to hook_cron()? I'm calling aggregator_cron() once and check if the feed has been updated.

3) The aggregator module's provided blocks.
Listing, displaying and configuring blocks is tested, I've found and fixed a related bug, #423886: aggregator_block_save fails with "Field 'description' doesn't have a default value".

4) aggregator_element_data().
Not part of aggregator.module

5) aggregator_refresh() with specified etag and modified.
I do execute the function indirectly with the cron test but not with anything specific. Also, the actual implementation has been moved outside aggregator.module

6) Update with no new syndicated content.
See 5.

7) Update to a moved feed.
See 5.

8) Make sure lines 607-609 use theme('image') instead of other stupid stuff.
That stuff has been moved to aggregator.parser.inc

9) Update to unparsable feeds.
See 5.

10) aggregator_parse_w3cdtf()
11) Trying to use aggregator_parse_feed() to parse invalid xml.
12) Update a feed with more than one new item.
13) Attempt to update to a feed with a duplicate item.
14) Update to a feed in a category.
See 8.

15) View feed items in a category.
See 1.

Also tested:
- API functions, for saving, updating and deleting categories
- sanitize function that checks if the configured "handlers" for fetching, parsing etc. are available and if not, resets to default

Berdir’s picture

Added some comments and remove self::$prefix, as we test in a separate db now, there is no reason to use some sort of prefix imho.

brianV’s picture

I wrote an aggregator.module patch that needs a test written in #404356: Aggregator should strip tags before using beginning of description tag as title. Unfortunately, I haven't completely figured the test interface out - I would really appreciate it if someone wouldn't mind writing a test for the patch.

alex_b’s picture

@Berdir, thanks for the updated list.

The tests you've added are looking very good, nice work. Here is an item by item break down that I did following your list and looking at the patch:

1) *DONE* Viewing aggregator/categories/* pages.
2) *Should also test expired items* Appropriate aggregator feeds periodically refreshing.
3) *DONE* The aggregator module's provided blocks.
4) *OPEN* aggregator_element_data().
5) *adressed by #364467: Remove-items followed by update items does not work* aggregator_refresh() with specified etag and modified.
6) *OPEN* Update with no new syndicated content.
7) *OPEN* Update to a moved feed.
8) *OPEN* Make sure lines 607-609 use theme('image') instead of other stupid stuff.
9) *OPEN* Update to unparsable feeds.
10) *OPEN* aggregator_parse_w3cdtf()
11) *OPEN* Trying to use aggregator_parse_feed() to parse invalid xml.
12) *OPEN* Update a feed with more than one new item.
13) *OPEN* Attempt to update to a feed with a duplicate item.
14) *DONE* Update to a feed in a category.
15) *DONE* View feed items in a category.

- In regards to 6), 7) and 9) there should be separate tests for these cases.
- We shouldn't remove items from the list only because they moved to different .module files.
- Could you lay down which cases you're going to address and create a follow up issue for those which won't be addressed by this patch? (Of course I'd encourage you to address all of them ;-)

Berdir’s picture

I agree that we should not remove items and I also think that more functions have been added since these lists have been created. There are already issues for other files, I'm going to create new follow-ups for the new files.

Looking at http://drupal.org/files/issues/aggregator_coverage.png, the following files need more tests:

Existing: (Several of the functions in those lists are also tested in this patch, because they use the api functions that are in aggregator.module)
#276499: Tests needed: aggregator.pages.inc
#276486: Tests needed: aggregator.admin.inc

New (I will post lists of tested functions when I'm starting with the tests there)
#456390: Tests needed: aggregator.fetcher.inc
#456402: Tests needed: aggregator.parser.inc
#456408: Tests needed: aggregator.processor.inc

Dries’s picture

I'm assigning this issue to alex_b. I'll commit it when alex_b marks it RTBC, and I'll let alex_b drive the process (if he wants to).

alex_b’s picture

Status: Needs review » Needs work
FileSize
11.68 KB

#14: OK

#13: I moved all open items from #12 to the new issues that you opened.

Which leaves us with:

1) *DONE* Viewing aggregator/categories/* pages.
2) *NEEDS WORK* Appropriate aggregator feeds periodically refreshing.
3) *DONE* The aggregator module's provided blocks.
14) *NEEDS WORK* Update to a feed in a category.
15) *DONE* View feed items in a category.

Am I missing one here?

The *NEEDS WORK* above indicate that:

2) testCron() should also test for expired items (as indicated in #12) and at a second look, I'd say it should also test whether the feed produced the expected numbers of feed items.
14) The association between feed and category shouldn't be created through a query (see db_insert() statement) but rather through the UI.

As I reviewed the patch, I did some minor code style adjustments here and there, mostly to comments and messages.

mustafau’s picture

Status: Needs work » Needs review
FileSize
12.51 KB

Reroll.

Status: Needs review » Needs work

The last submitted patch failed testing.

Berdir’s picture

Status: Needs work » Needs review
FileSize
14.84 KB

Finally :)

2) testCron() should also test for expired items (as indicated in #12) and at a second look, I'd say it should also test whether the feed produced the expected numbers of feed items.

Added both.

14) The association between feed and category shouldn't be created through a query (see db_insert() statement) but rather through the UI.

Changed.

Status: Needs review » Needs work

The last submitted patch failed testing.

Berdir’s picture

Status: Needs work » Needs review
FileSize
14.86 KB

I shall not change the tests before making the patch...

Status: Needs review » Needs work

The last submitted patch failed testing.

Berdir’s picture

Status: Needs work » Needs review
FileSize
19.51 KB

cron handling changed as it does now use DrupalQueue.

Updated the test case to call drupal_cron_run() instead of aggregator_cron() so that the queues are actually executed.

Status: Needs review » Needs work

The last submitted patch failed testing.

mustafau’s picture

Status: Needs work » Needs review
FileSize
14.45 KB

Removing accidental code coverage parts from the patch.

Status: Needs review » Needs work

The last submitted patch failed testing.

mustafau’s picture

Status: Needs work » Needs review
FileSize
14.46 KB
grndlvl’s picture

+++ modules/aggregator/aggregator.test	17 Oct 2009 14:42:36 -0000
@@ -287,6 +291,37 @@
+    // Confirm that the block was moved to the proper region.
+    $this->assertText(t('The block settings have been updated.'), t('Block successfully moved to %region_name region.', array('%region_name' => 'sidebar_first')));

@@ -513,6 +599,103 @@
+    // Confirm that the block was moved to the proper region.
+    $this->assertText(t('The block settings have been updated.'), t('Block successfully moved to %region_name region.', array('%region_name' => 'sidebar_first')));

These two don't check that the block was added to the correct region and that is not that necessary to figure out if they were added to the correct region. The other checks right after should be sufficient in determining if the block was enabled.

I left in tests just in case.

+++ modules/aggregator/aggregator.test	17 Oct 2009 14:42:36 -0000
@@ -638,3 +821,35 @@
+/**
+ * Test the pluggable architecture.
+ */
+class PluggableTestCase extends AggregatorTestCase {
+  public static function getInfo() {
+    return array(
+      'name' => 'Fetcher, parser and processor',
+      'description' => 'Test the default fetcher, parser and processor and related functions.',
+      'group' => 'Aggregator',
+    );
+  }
+
+  /**
+   * Test the sanitize function.
+   */
+  function testSanitize() {
+    $this->assertFalse(aggregator_sanitize_configuration(), t('Pluggable configuration is correctly set up.'));
+
+    variable_set('aggregator_fetcher', 'broken');
+    $this->assertTrue(aggregator_sanitize_configuration(), t('Pluggable configuration has been sanitized.'));
+    $this->assertEqual(variable_get('aggregator_fetcher', 'aggregator'), 'aggregator', t('Configuration has been corrected.'));
+
+    variable_set('aggregator_parser', 'broken');
+    $this->assertTrue(aggregator_sanitize_configuration(), t('Pluggable configuration has been sanitized.'));
+    $this->assertEqual(variable_get('aggregator_parser', 'aggregator'), 'aggregator', t('Configuration has been corrected.'));
+
+    variable_set('aggregator_processors', array('aggregator', 'broken'));
+    $this->assertTrue(aggregator_sanitize_configuration(), t('Pluggable configuration has been sanitized.'));
+    $this->assertEqual(variable_get('aggregator_processors', array('aggregator')), array('aggregator'), t('Configuration has been corrected.'));
+  }
+}

I am not aware of this feature so I am not sure what this is doing. It also needs additional comments.

I have added some additional comments.
All looks good. Except the above items mentioned.

Thanks,

Jonathan

I'm on crack. Are you, too?

sun.core’s picture

Priority: Critical » Normal

Sorry, but tests don't qualify as critical anymore.

aspilicious’s picture

Can someone review this?

cwgordon7’s picture

#27: 276493-27_aggregator_tests.patch queued for re-testing. (This was last tested over a year ago and I would be surprised if it still applied, let alone passed. I'm not even sure if this is necessary anymore).

retester2010’s picture

Status: Needs review » Needs work
+++ modules/aggregator/aggregator.test	10 Dec 2009 15:34:40 -0000
@@ -418,6 +456,48 @@ class UpdateFeedItemTestCase extends Agg
+    $this->createSampleNodes();
+    ¶
+    $updated_count = db_query("SELECT COUNT(*) FROM {aggregator_item} WHERE fid = :fid", array(':fid' => $feed->fid))->fetchField();

trailing white space

40 critical left. Go review some!

Jody Lynn’s picture

Version: 7.x-dev » 8.x-dev
webchick’s picture

Issue tags: +Needs tests

.

Berdir’s picture

Wondering why this has been pushed to 8.x :) What's the policy for test additions?

I see no reason to not add them to a stable version. If nothing else, it helps to increase stability and it's doesn't count as an API change for me.

Sure, it should be added to 8.x first and then backported, but there is no 8.x branch just yet :)

Jody Lynn’s picture

Version: 8.x-dev » 7.x-dev
Rodgey’s picture

This bug might add some light to the case:

reproducing the bug:

1 - create more than 1 catagory in the feed aggregator.
2 - add a feed item (you might use f.e. "http://online.wsj.com/xml/rss/3_7085.xml")
!important: check more than one catagory.
3 - run update for this feed

bug 1:

You will now find out that the items are just catagorized for one catagory instead of the multiple catagories that you've put with a checkbox while adding the feed.

4 - click on the feed name in the feed overview
5 - choose catagorize
6 - add the checkboxes (again) for multiple catagories

Bug 2

Now the rss feed will be shown in multiple catagories, but cron won't run anymore and produce the following error:

PDOException: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-281' for key 1: UPDATE {aggregator_category_item} SET cid=:db_update_placeholder_0 WHERE ( (iid = :db_condition_placeholder_0) ); Array ( [:db_update_placeholder_0] => 1 [:db_condition_placeholder_0] => 281 ) in aggregator_save_item() (line 170 of /***/aggregator/aggregator.processor.inc).

I've been experimenting a little and found that the index data from aggregator_feed_item in the db are blocking cron to run.

Berdir’s picture

Status: Needs work » Needs review
FileSize
23.42 KB

I am able to reproduce the first bug reported in #36, and updated the tests to account for this.

Also did some other refactoring, removed whole test class that is already covered by another one and added a createCategory() helper function.

The tests will fail, will upload a patch that fixes it here: #1023190: Wrong merge query in aggregator_save_item()

Status: Needs review » Needs work

The last submitted patch, 276493-28_aggregator_tests.patch, failed testing.

Berdir’s picture

Version: 7.x-dev » 8.x-dev
Issue tags: +Needs backport to D7
bfroehle’s picture

Status: Needs work » Needs review

#37: 276493-28_aggregator_tests.patch queued for re-testing.

Berdir’s picture

Yay, now they pass ;)

aspilicious’s picture

Can someone review this test case?

bfroehle’s picture

At a minimum there are a few whitespace mistakes.

Berdir’s picture

Re-rolled with the trailing whitespaces removed.

This patch will never be perfect, there is stuff that still isn't tested and there is a lot of old code in aggregator.test that can't all be cleaned up.

So my suggestion would be to try to get this commited rather sooner than later, especially so that it can be added to D7 too. Who knows what will happen with aggregator.module in D8...

Berdir’s picture

Uhm, with patch this time.

Lars Toomre’s picture

I thought that I could help review this patch to speed it along, but I am unable to find where on drupal.org the current reference file aggregator.test is stored. Could someone possibly post the URL of the reference file?

In looking at the entirely new TestCron function, I had a couple of thoughts:

1) After adding an old feed item, I think that we should assert that the data base now contains one feed item. In essence, demonstrate started at zero, incremented by one and then cron went through and cleaned up the old feed item returning to zero records in the data base.

2) I did not understand where the 'cid' value of 19 comes from in aggregator_category_item. An inline comment would be appropriate here.

3) I was puzzled where the value of 5 came from in the '5 new feed items' test came from. I am guessing that it is the number of items in the default feed. If that is the case, why not use $this->getDefaultFeedItemCount() instead of a hard coded value of 5.

4) Generally I think it is better to gather/compute the value for the test and then do the assertion test. Hence, I would reorder the code lines at the bottom of TestCron().

5) Based upon the problems I have seen with the aggregator feed in cron, I would check for two further conditions in this test subroutine.

5a) After the five feed items have been added, I would suggest that we mimic the passage of time and it is now time for another cron run. Run cron and attempt to retrieve/process the same feed. There should still be 5 feed items in the data base when this completes, confirming that no duplicates were added. I believe the TIMESTAMPs for these items should remain equal to REQUEST_TIME.

5b) After successfully finishing the 5a) test, I would manually delete one of the middle records, like the third feed record for instance. I would then simulate the passage of time and do another cron run to confirm that the one 'missing' feed item has been added back to the data bases with the new simulated time.

With the above changes, I think we can affirmatively confirm that cron can create Create/Update/Delete feed items with aged, new and duplicate feed items.

The one further problem that I have encountered deals with the case when a node body has been updated for clarification or to change a spelling error sometime after the node is published and included in the original rss.xml. I would hope that the feed item in the aggregator data base would be updated in a cron job for this small spelling change. Does it make sense to add this case as an assertion test in TestCron() as well?

Eric_A’s picture

Could someone possibly post the URL of the reference file?
http://drupalcode.org/project/drupal.git/blob/HEAD:/modules/aggregator/a...

Use the "raw"-hyperlink if you need plain code.

Lars Toomre’s picture

Thank you Eric_A. The new git system has me confused when just wanting to review raw source code.

Berdir’s picture

#45: 276493-29_aggregator_tests.patch queued for re-testing.

Status: Needs review » Needs work
Issue tags: +Needs tests, +Needs backport to D7

The last submitted patch, 276493-29_aggregator_tests.patch, failed testing.

EclipseGc’s picture

Also, check to make sure that all the potential pseudo-dependencies are enabled, as block deletion is part of the logic here, but it's often wrapped in a module_exists check and so code that should have testing coverage doesn't get fired.

We ran into this with Blocks as Plugins. Aggregator had direct calls to delete blocks from the blocks table, which we abandoned months ago, but never got errors on out of aggregator tests. I just found it as we were doing a last pass of manual testing.

Eclipse

Pat Redmond’s picture

Assigned: Unassigned » Pat Redmond
Issue tags: +sydney2013

Working on tests at Drupalcon Sydney 2013

Pat Redmond’s picture

Assigned: Pat Redmond » Unassigned
Status: Needs work » Needs review
FileSize
2.2 KB

The recent PSR-0 change means that the test coverage in the patches above don't apply correctly (since tests have moved in the directory structure) so this patch starts the process of creating tests that adhere to PSR-0.

Based on the test coverage outlined in the issue summary, the attached patch addresses the following:
1) Viewing aggregator/categories/* pages.

The following items have been addressed at another stage:

The following items require further review (they might be already included in the latest 8.x branch but they also may need to be be implemented):
2) Appropriate aggregator feeds periodically refreshing.
3) The aggregator module's provided blocks.
4) aggregator_element_data().
5) aggregator_refresh() with specified etag and modified.
6) Update with no new syndicated content.
7) Update to a moved feed.
8) Make sure lines 607-609 use theme('image') instead of other stupid stuff.
9) Update to unparsable feeds.
10) aggregator_parse_w3cdtf()
11) Trying to use aggregator_parse_feed() to parse invalid xml.
12) Update a feed with more than one new item.
13) Attempt to update to a feed with a duplicate item.
14) Update to a feed in a category.
15) View feed items in a category.

Pat Redmond’s picture

Issue summary: View changes

Noting that the first test required has been addressed by post 52

Pat Redmond’s picture

Issue summary: View changes

Updated issue summary to reflect that there is a test which checks that cron runs and updates aggregator feeds correctly

Pat Redmond’s picture

Issue summary: View changes

Updated issue summary to reflect that there is a test which checks that the aggregator blocks are working

Pat Redmond’s picture

Issue summary: View changes

Updated issue summary- fix typo

Status: Needs review » Needs work
Issue tags: -Needs tests, -Needs backport to D7, -sydney2013

The last submitted patch, aggregator-test-category-pages-276493-52.patch, failed testing.

Anonymous’s picture

Issue summary: View changes

Updated issue summary to show the files providing the functionality

lokapujya’s picture

Category: Bug report » Task
Issue summary: View changes
Issue tags: -sydney2013
FileSize
4.25 KB

Missing test coverage isn't a bug, right?

The last patch is no longer relevant since #2127725: Remove category handling from aggregator

Keeping some comments from #45.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.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.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.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.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.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.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should 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.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should 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.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should 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.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.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: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should 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: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev
quietone’s picture

Project: Drupal core » Aggregator
Version: 9.3.x-dev » 1.x-dev
Component: aggregator.module » Code

The aggregator module has been removed from Core in 10.0.x-dev and now lives on as a contrib module. Issues in the Core queue about the aggregator module, like this one, have been moved to the contrib module queue.

larowlan’s picture

Status: Needs work » Closed (outdated)

We're keeping the lights on here now aggregator is out of core.

I think at this point we're likely to only add new tests for new bugs/features.

Given the age of this patch, going to close as outdated.

Thanks everyone for their efforts to this point.