-
Notifications
You must be signed in to change notification settings - Fork 0
Development Process
This project follows the general development guidelines outlined in the VR4VET project.
- Agile Workflow: See Agile Workflow in VR4VET
- Coding Conventions: See Coding Conventions
- Naming Conventions: See Naming convention
(Add details specific to setting up and running the chat-service locally, e.g., Python version, dependencies, virtual environments, running tests.)
You can find dependencies in requirements.txt.
Tests are located in the tests/ directory and can be run using pytest.
See pytest.ini for configuration.
Key test files:
test_embeddings.pytest_dao.pytest_document_upload.pytest_endpoints.py
While detailed test execution reports are typically managed as part of the continuous integration and testing workflow, the format for such reports, especially for functional and quality requirements, is outlined in the Test Report Template. This template guides the documentation of test specifics, including requirement IDs, tester, date, duration, evaluation, and other relevant metrics for quality attribute testing.
- Create issues for new features or bugs.
- Follow the branching strategy (e.g., feature branches from
develop). - Submit Pull Requests for review.
Authors:
Peter Olai Johnsen
Tobias Fremming
Erik Le Blanc Pleym
About Chat-Service
Core Components
Development
Codebase Details
- Codebase Architecture
- Routes
- Command-py
- Config-py
- Context Upload-py
- LLM-py
- Main-py
- Pipeline-py
- Streaming WS-py
- Transcribe-py
Deployment and Operations