Cover the module with tests

Yes it would be great @AstonVictor

Created a new MR.

Implemented a simple test to check the output for nodes.

Hi @AstonVictor,
thank you for your work. I'm just unsure about this piece of code:

// Enable prevnext links for node entity type.
$config = \Drupal::configFactory()->getEditable('prevnext.settings');
$config->set('prevnext_enabled_entity_types', ['node' => 'node']);
$config->set('prevnext_enabled_entity_bundles', ['node' => ['prevnext' => 'prevnext']]);
$config->save();

I'm not sure if changing config values during tests is a best practice, but maybe I'm wrong.

Hi @aronne,

we change configs only for test env. Configs on the /admin/config/user-interface/prevnext won't be affected.
you can even run the test with the disabled module because it will be enabled for tests - protected static $modules = ['node', 'prevnext'];

FYI you can find editing configs in the same way for tests in some core modules as well e.g. UserPasswordResetTest

\Drupal::configFactory()->getEditable('user.flood')
 ->set('user_limit', 3)
 ->save();

thanks

Hi @AstonVictor,
Patch applied

AstonVictor → closed merge request !23

Automatically closed - issue fixed for 2 weeks with no activity.