calendar-plugin/compatibility-layer
Adrian Stephens 8d805ca8dc moving from svn 2026-04-02 09:44:38 +01:00
..
__pycache__ moving from svn 2026-04-02 09:44:38 +01:00
wp-emu-root/wp-admin/includes moving from svn 2026-04-02 09:44:38 +01:00
README.md moving from svn 2026-04-02 09:44:38 +01:00
caldav_client_compat_smoke.sh moving from svn 2026-04-02 09:44:38 +01:00
e2e_wp_emulation.php moving from svn 2026-04-02 09:44:38 +01:00
init.sh moving from svn 2026-04-02 09:44:38 +01:00
reset.sh moving from svn 2026-04-02 09:44:38 +01:00
run.sh moving from svn 2026-04-02 09:44:38 +01:00
security_smoke.sh moving from svn 2026-04-02 09:44:38 +01:00
seed.sh moving from svn 2026-04-02 09:44:38 +01:00
server.py moving from svn 2026-04-02 09:44:38 +01:00
smoke.sh moving from svn 2026-04-02 09:44:38 +01:00
ui_e2e.sh moving from svn 2026-04-02 09:44:38 +01:00
ui_e2e_wp_emulation.php moving from svn 2026-04-02 09:44:38 +01:00
wp_emulation.php moving from svn 2026-04-02 09:44:38 +01:00

README.md

Compatibility Layer

This directory is the canonical local WordPress emulation entrypoint.

Purpose:

  • run the stand-alone harness used for local deterministic testing
  • keep emulation tooling out of deployable plugin code (code/)

Current implementation delegates to the existing harness implementation under fixture/.

Primary commands from repository root:

./compatibility-layer/reset.sh
./compatibility-layer/seed.sh
./compatibility-layer/run.sh

Optional archived local checks (fixture-era):

./compatibility-layer/smoke.sh
./compatibility-layer/security_smoke.sh

These delegate to scripts under fixture-tests/. Active development validation now targets the remote server first.