| title | Week #4 |
|---|
Summary of testing strategy and types of tests implemented. Our team developed, and research project's QA aspects from first capstone week so, we have multiple testing scenarious, because our project is consist of complex components, which really need QA testing. In our project we have:
- Graph generation testing
- Basic Unit testing
- Vector RAG testing
- Docker Compose Configuration testing
- Linting and styling checks
Automated Security Scanner for repository find vulnerabilities in code logic.
Checks if docker compose can prorerly configure, build and run using default configuration.
Check code styling and linting uses pre-commit configuration.
Workflow When pull request is approved by person sends cute bear picture into comments to congradulate with approval and readiness for merge.
Workflow Checks pr title with conventional rules, because that we use squashing ruleset into main (protected) branch.
Workflow Checks pr title with conventional rules, because that we use squashing ruleset into main (protected) branch.
As deployment we do not need any deployment now, but in near future we will create docker image building and publishing into register.
Now we are feeling exited by project, we are currently adding more and more complex features into project, but feeling a bit tired and overwhelmed with a lot of tasks and deals we need to implement in near future.
- Add Pytest
Add pytest framework for testing infrastructure - Parse Async Functions
Added support for asynchronous function parsing - [Generator] Connect Files to Folders nodes
Implemented file-to-folder mapping in generator component
- Essential Integration Tests
Developed core integration tests for critical paths - CI: Graph Generation Auto Testing
Set up automated graph testing in CI pipeline
- Classical Vector RAG approach Introduce Vector RAG approach in project
- Research: Efficiency information search in codebases
Investigating optimization techniques for code search
- Week 4 Report
Compiling weekly progress metrics and findings
We confirm that the code in the main branch:
- In working condition.
- Run via docker-compose (or another alternative described in the
README.md).


