HSLG Media

docs-publisher-test.php

docs-publisher-test.php

Source file: tests/backend/docs-publisher-test.php

Module: tests-backend

Size: 90 lines

SHA-256: 29c87b161195feef005c07b07a6a6a90c6547d7dca448363053f6f8a5f1e2982

Responsibility

Checks PHP backend assumptions; database doubles are not live MariaDB evidence.

Declared entry points

  • WP_Error — source line 5.
  • is_wp_error — source line 6.
  • current_user_can — source line 11.
  • wp_revisions_enabled — source line 12.
  • wp_slash — source line 13.
  • get_post — source line 14.
  • get_post_status — source line 15.
  • get_post_meta — source line 16.
  • update_post_meta — source line 17.
  • get_posts — source line 18.
  • get_page_uri — source line 19.
  • get_page_by_path — source line 20.
  • wp_insert_post — source line 21.
  • wp_delete_post — source line 22.
  • wp_update_post — source line 23.
  • ensure — source line 25.
  • get_option — source line 49.
  • update_option — source line 50.
  • register_activation_hook — source line 51.
  • add_action — source line 52.
  • wp_next_scheduled — source line 53.
  • wp_schedule_single_event — source line 54.
  • esc_html — source line 55.

Imports and dependencies

  • Line 24: require dirname(__DIR__,2).'/wordpress/hslg-docs-publisher/src/Publisher.php';
  • Line 56: require dirname(__DIR__,2).'/wordpress/hslg-docs-publisher/src/AutoSync.php';

Behaviour and audit locations

  • Line 90: echo "HSLG docs auto publisher: activation, idempotence, conflicts, retry and ZIP upgrade passed\n";

Relationship to the system

This page is the file-level source reference, not the architecture rationale. Read the module explanation, the corresponding architecture decision and user guide before changing behaviour. Names and line locations above are extracted from this exact source version; they are reference points, not proof that an external service or a phone feature works.

Change verification

Review the entry points and errors in this file, then run the module’s associated tests, source dependency gate, history gate and documentation coverage check. If the file changes an API response, user interaction, data model, deployment or third-party dependency, revise those human explanations and disaster recovery/licensing when relevant. Do not infer actual native or external API operation from source presence.