Enhance CI/CD Pipeline with Unit Tests and Static Code Analysis

[kursataktas]

As we ship new features, the testing effort has increased dramatically, and the possibility of creating edge-case bugs has also risen. We should consider improving our CI/CD pipeline to include unit tests and code quality checks.

Actions:

1. Implement unit tests for both the frontend and backend, and add a coverage threshold to the pipeline.
2. Add a static code analysis tool to the pipeline to detect unintended methods, imports, etc.

[costas80]

Thought I'd chime in on one point here that could be helpful:

Add a static code analysis tool to the pipeline to detect unintended methods, imports, etc.

Given that Gurubase is open source you could benefit from Sonarcloud for free (see here). This would cover unit tests, coverage, code quality etc. You can then add to this your own SCA jobs covering things like library licence checks and vulnerabilities.

[kursataktas]

Thought I'd chime in on one point here that could be helpful:

Add a static code analysis tool to the pipeline to detect unintended methods, imports, etc.

Given that Gurubase is open source you could benefit from Sonarcloud for free (see here). This would cover unit tests, coverage, code quality etc. You can then add to this your own SCA jobs covering things like library licence checks and vulnerabilities.

I didn't know that Sonarcloud offers a free package for OSS. Thanks for the heads-up, I'll look into it.