mirror of
https://github.com/saltbo/zpan.git
synced 2026-08-29 00:01:42 +08:00
saltbo
118 lines
3.6 KiB
Gherkin
118 lines
3.6 KiB
Gherkin
Feature: Branding
|
|
Pro instances customize their wordmark, theme colors, and logo (white-label).
|
|
Configz serves the active look without authentication.
|
|
|
|
@branding/defaults @api
|
|
Scenario: Unconfigured branding returns defaults
|
|
Given no branding is configured
|
|
When configz is requested
|
|
Then default branding is returned
|
|
|
|
@branding/public @api
|
|
Scenario: Branding is public
|
|
Given configured branding
|
|
When configz is requested without authentication
|
|
Then it is still returned
|
|
|
|
@branding/stored-values @api
|
|
Scenario: Stored branding is served
|
|
Given stored branding values
|
|
When configz is requested
|
|
Then the stored values are returned
|
|
|
|
@branding/legacy-url-compat @api
|
|
Scenario: Legacy absolute-URL logo and favicon are still served
|
|
Given stored branding with absolute-URL logo and favicon
|
|
When configz is requested
|
|
Then the absolute URLs are returned unchanged
|
|
|
|
@branding/custom-theme @api
|
|
Scenario: Custom theme colors are served
|
|
Given stored custom theme colors
|
|
When configz is requested
|
|
Then the custom theme values are returned
|
|
|
|
@branding/white-label-gated @api
|
|
Scenario: White-label requires Pro
|
|
Given an instance without the white_label feature
|
|
When an admin updates branding
|
|
Then the API responds 402
|
|
|
|
@branding/multipart-required @api
|
|
Scenario: Branding updates must be multipart
|
|
Given an admin with Pro
|
|
When they PUT a non-multipart body
|
|
Then the API responds 415
|
|
|
|
@branding/wordmark-length @api
|
|
Scenario: Wordmark text is length-limited
|
|
Given an admin with Pro
|
|
When they submit a wordmark longer than 24 chars
|
|
Then the API responds 422
|
|
|
|
@branding/save-text @api
|
|
Scenario: Wordmark and powered-by settings are saved
|
|
Given an admin with Pro
|
|
When they save wordmark text and hide-powered-by
|
|
Then the settings are persisted
|
|
|
|
@branding/builtin-theme @api
|
|
Scenario: A built-in theme can be selected
|
|
Given an admin with Pro
|
|
When they select a built-in theme
|
|
Then the theme is saved
|
|
|
|
@branding/save-custom-theme @api
|
|
Scenario: Valid custom theme colors are saved
|
|
Given an admin with Pro
|
|
When they save valid custom colors
|
|
Then the colors are persisted
|
|
|
|
@branding/invalid-colors @api
|
|
Scenario: Invalid custom colors are rejected
|
|
Given an admin with Pro
|
|
When they submit invalid custom colors
|
|
Then the API responds 422 and the stored theme is unchanged
|
|
|
|
@branding/logo-upload @api
|
|
Scenario: A logo is stored as a data URI
|
|
Given an admin with Pro and no public storage
|
|
When they upload a valid logo
|
|
Then it is stored as a base64 data URI and returned unchanged
|
|
|
|
@branding/favicon-upload @api
|
|
Scenario: A favicon is stored as a data URI
|
|
Given an admin with Pro
|
|
When they upload a valid favicon
|
|
Then it is stored as a base64 data URI carrying its mime type
|
|
|
|
@branding/logo-mime @api
|
|
Scenario: Logo type is validated
|
|
Given an admin with Pro
|
|
When they upload an invalid logo type
|
|
Then the API responds 400
|
|
|
|
@branding/logo-size @api
|
|
Scenario: Logo size is limited
|
|
Given an admin with Pro
|
|
When they upload a logo larger than 256KB
|
|
Then the API responds 413
|
|
|
|
@branding/favicon-size @api
|
|
Scenario: Favicon size is limited
|
|
Given an admin with Pro
|
|
When they upload a favicon larger than 64KB
|
|
Then the API responds 413
|
|
|
|
@branding/admin-only @api
|
|
Scenario: Only admins update branding
|
|
Given a non-admin user
|
|
When they update branding
|
|
Then the API responds 403
|
|
|
|
@branding/reset-field @api
|
|
Scenario: A branding field can be reset
|
|
Given stored branding
|
|
When an admin resets a text field
|
|
Then the field is cleared
|