avoid exporting updateSettingsValues

client/data/settings/actions.js

@@ -13,7 +13,7 @@ import { __ } from '@wordpress/i18n';
 import ACTION_TYPES from './action-types';
 import { NAMESPACE, STORE_NAME } from '../constants';
 
-export function updateSettingsValues( payload ) {
+function updateSettingsValues( payload ) {
 	return {
 		type: ACTION_TYPES.SET_SETTINGS_VALUES,
 		payload,

client/data/settings/test/actions.js

@@ -7,11 +7,7 @@ import { apiFetch } from '@wordpress/data-controls';
 /**
  * Internal dependencies
  */
-import {
-	saveSettings,
-	updateIsSavingSettings,
-	updateSettingsValues,
-} from '../actions';
+import { saveSettings, updateIsSavingSettings } from '../actions';
 
 jest.mock( '@wordpress/data' );
 jest.mock( '@wordpress/data-controls' );
@@ -84,12 +80,13 @@ describe( 'Settings actions tests', () => {
 			// Simulate the response from the apiFetch call and proceed to the next yield
 			// Since the actual fetching process is mocked, pass the apiResponse to the next saveGenerator step directly
 			next = saveGenerator.next( apiResponse );
-			expect( next.value ).toEqual(
-				updateSettingsValues( {
+			expect( next.value ).toEqual( {
+				type: 'SET_SETTINGS_VALUES',
+				payload: {
 					payment_method_statuses:
 						apiResponse.data.payment_method_statuses,
-				} )
-			);
+				},
+			} );
 
 			next = saveGenerator.next(); // Skip the success notice
 			next = saveGenerator.next(); // Move to updateIsSavingSettings(false)