How areso/oblache works
Project type and purpose
• From the file tree and README, “Oblache” is not a full-stack repo but a dedicated automated test suite (API + UI) for a separate issue/feature-tracker application. Key indicators:
• tests_api/ and tests_ui/ directories containing pytest fixtures, page objects, HTTP utils, etc.
• .github/workflows definitions for api.yml, ui.yml, full_report.yml, etc.
• Dockerfile and docker-compose.yml to containerize the tests.
File structure
• Top-level files and folders:
• .github/workflows/ – CI jobs that build Docker images and launch tests.
• Dockerfile & docker-compose.yml – the environment in which tests run.
• requirements.txt – Python dependencies (pytest, requests, selenium, etc.).
• conftest.py – shared fixtures for all pytest runs.
• tests_api/ – API test suite using HTTP-based utils, data sources, logger, HTML report generators.
• tests_ui/ – UI test suite using the Page Object Model (base_page.py, login_page.py, etc.), Selenium locators, and browser drivers.
• manual tests ui/ – markdown test cases for manual verification.
README for additional insights
• README.md describes this as a “public issue and feature tracker” test project with links to design_doc.md and API references.
• README_TESTS.md likely outlines how to run and structure tests.
Callouts and details
• That conftest.py provides shared fixtures (base URLs, browser sessions) used by both suites.
• That tests_api/data drives data-driven testing.
• That manual tests UI live outside the automated pipeline but feed into the same page object abstractions if later automated.
• Optionally, note capacity.yml for load/performance tests as a separate CI job calling tests_api/try_performance.py.