Notes editor: integration test checklist

The notes editor prototype is frontend-only. It keeps notes in localStorage and fakes saving and sharing. Use this list when it is wired to the Testpress Python backend. Section A is what the backend must supply. The other sections are things to re-verify in the real UI.

A. Backend and data requirements (faked in the prototype)

Notes

Folders and tags

Shared with me (read-only)

Search

General

B. Integration with the real Testpress page

C. Editor behaviour to re-test

Title and focus

Slash menu

Bubble menu (desktop)

Formatting and shortcuts

Tables

Callout and toggle

Read-only mode

Keyboard help

D. Library, nav and list

Layouts

Nav pane

Folder and tag popovers

Note list

Meta line (under the title)

E. Mobile and touch (needs real iOS and Android devices)

The prototype was only tested with browser emulation.

F. Accessibility

G. Visual and theming

H. Security and robustness

I. Known gaps and decisions to settle before integration

  • Images and attachments in notes are not built.
  • Real sharing, comments and collaboration aren't built. Shared notes in the prototype are fixed seed data.
  • No real conflict resolution or multi-device sync.
  • The simulated panels (sim-shortcuts and the prototype panel) must be removed.
  • Search is a client-side substring match over local data.
  • The pin limit, trash retention and tag and folder naming rules need product decisions.
  • iOS and Android behaviour and IME input are untested on real hardware.
  • Not checked after the Tailwind conversion: dark mode on the mobile "Turn into" menu and the slash-menu sample blocks (checklist, callout, toggle, table), plus small leftover mobile screenshot shifts.