Test with WordPress 7.0 and update "Tested up to"

[mayukojpn]

WordPress 7.0.2 is the current release, while this plugin's Tested up to is 6.7.5. This issue covers verifying the plugin against a current WordPress install and updating the value in readme.txt.

Steps

1. Set up a WordPress 7.0.x environment (wp-env or equivalent)
2. Run through the plugin's main features and confirm no fatal errors or warnings appear
3. Update Tested up to in readme.txt
4. Release and deploy to WordPress.org

Note

WordPress.org shows a notice on the plugin page when Tested up to falls behind the three most recent major releases, so keeping this value current also keeps the listing clean.

Reference

• Plugin page: https://wordpress.org/plugins/taro-ad-fields/
• Current Tested up to: 6.7.5
• Latest WordPress: 7.0.2

[mayukojpn]

Ran the plugin against WordPress 7.0.2. No problems attributable to this plugin were found.

Environment

WordPress	7.0.2
PHP	8.3.33
Setup	wp-env from this repo's .wp-env.json
Plugin version	working tree at 0cfaaee

Results

Check	Result
Plugin activation	OK
PHPUnit (npm test)	2 tests, 8 assertions, all passing
php -l on every plugin file under PHP 8.3	No syntax errors
Deprecated WordPress functions	0 of the 242 functions in wp-includes/deprecated.php are called (8 files, 141 identifiers scanned)
debug.log after a clean run	Empty — no fatals, warnings, notices or deprecations
Admin screens	6 screens loaded, HTTP 200, no errors rendered
Front-end pages	HTTP 200, no errors

Admin screens covered: dashboard, ad-content list, new/edit post, ad-position and ad-context term screens, Writing settings, Widgets.

Functional checks

Feature	Result
ad-content post type	Registers; create and query work
taf_register_positions()	5 terms created (head, after_content, body_open, in_footer, iframe)
taf_render()	Returns the ad markup; $before / $after wrappers applied correctly
taf_render() with an unregistered position	Returns an empty string, as intended
taf_iframe_url()	Generates a valid URL; the endpoint responds 200
taf_available_display_mode()	Correct for both valid and invalid input
TafWidget	Registered and listed on the Widgets screen

One thing worth recording

/wp-admin/widgets.php returns HTTP 500 under the default theme. This is not a plugin problem: Twenty Twenty-Five is a block theme with no registered sidebars, and WordPress itself responds with "The theme you are currently using is not widget-aware". Switching to Twenty Twenty returns HTTP 200 with TafWidget listed as expected. Noting it here so the next person who sees that 500 does not spend time on it.

Requirements are consistent

WordPress 7.0 requires PHP 7.4 and the plugin header declares Requires PHP: 7.4, so there is no conflict. README.md currently states Tested up to: 6.8.

Limits of this check

• Automated coverage is thin — 2 tests. Their passing says little on its own; the error-log and screen-load results carry more weight here.
• Admin screens were fetched and scanned for rendered errors, but not visually inspected. Layout or JavaScript problems would not have been caught.
• Exercised through WP-CLI and HTTP requests rather than by clicking through the UI, so interaction-driven paths (saving a meta box through the editor, drag-and-drop widget placement) are untested.

Suggestion

The evidence supports updating Tested up to to 7.0 in README.md. Leaving the decision to the maintainers, since the checks above do not cover editor interactions.