test: update pytest configuration

.vscode/settings.json

@@ -0,0 +1,6 @@
+{
+    "sonarlint.connectedMode.project": {
+        "connectionId": "http-localhost-9000",
+        "projectKey": "my_ghost_writer"
+    }
+}

CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+# 0.5.2
+
+- Improved docker build process to fix HuggingFace space deploy
+- Read API to get thesaurus functionality
+- Added adding custom voices (write API) to the thesaurus functionality
+- updated backend tests
+- updated frontend tests
+
 ## 0.3.0
 
 - add an installation script (python required), mostly useful for lite.koboldai.net users

pyproject.toml

@@ -40,7 +40,7 @@ uvicorn = "^0.34.2"
 pymongo = {extras = ["srv"], version = "^4.13.2"}
 
 [tool.pytest.ini_options]
-addopts = "--cov=my_ghost_writer --cov-report html"
+addopts = "--cov=my_ghost_writer --cov-report=term-missing"
 
 [build-system]
 requires = ["poetry-core>=2.0.0,<3.0.0"]

tests-prompts/frontend-accessibility.md

@@ -0,0 +1,39 @@
+# Improve the frontend accessibility, also for writing better playwright tests
+
+You are tasked with incrementally improving the accessibility and maintainability of a vanilla HTML/JS/CSS codebase. Follow these guidelines:
+
+## Code deduplication
+
+- there are some functions like `createButtonById()`, `createSelectWithOptListById()`, `createElementById()`
+
+## Semantic HTML, ARIA, and Data Attributes
+
+- Prefer semantic HTML elements (e.g., `<button>`, `<a>`, `<header>`, `<nav>`, etc.) for structure and interactivity.
+- Use ARIA attributes to enhance or clarify accessibility, especially when semantic HTML alone is not sufficient. Semantic HTML and ARIA can be used together.
+- If neither semantic HTML nor ARIA attributes are suitable for identification or testing, use custom data-* attributes (e.g., `data-testid`, `data-label`), especially to support Playwright test selectors and avoid breaking the test suite.
+
+## Accessibility Best Practices
+
+- Ensure all interactive elements are keyboard-accessible.
+- Provide visible focus indicators for interactive elements.
+- Use sufficient color contrast for text and UI elements.
+- Ensure form elements have associated labels.
+- Use descriptive link/button text.
+- Add alt text to images and icons.
+- Refactor duplicated code into reusable functions or components.
+
+## Incremental Changes
+
+- Make one small, focused change at a time.
+- After each change, update the Playwright test suite to reflect the modification and verify accessibility improvements.
+- Never break the Playwright test suite; preserve or update `data-*` attributes as needed for selectors.
+
+## Test Suite Updates
+
+- After every code change, review and update Playwright tests to match the new code and cover new accessibility features.
+- Ask the user for review and approval.
+
+## General Guidance
+
+- Do not distort the original JS/HTML/CSS logic or design.
+- Suggest other accessibility and code quality best practices as you proceed.