Quality dashboard: backend fix to enable mongo-only mode, security fix, disable old SQL, fix UI API, add mock data - #50
Merged
Conversation
GervaisETS
changed the title
Valeeeu
self-requested a review
March 11, 2026 23:52
Valeeeu
approved these changes
Mar 11, 2026
BEDDAR
approved these changes
Mar 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This Pull Request introduces a full configuration update to enable the Mongo-only execution mode for the Équipe 5 backend (Test Result Dashboad - Équipe 6) service in the TAF project.
Previously, the backend attempted to load SQL/JPA auto‑configuration, triggered Hibernate, created datasource objects, and produced errors when no PostgreSQL instance was available.
This PR applies all required changes so the backend runs cleanly using only MongoDB, with SQL components fully disabled. It also introduces a profile‑based security configuration, a proper Spring Boot profile (mongo), and safer environment variable handling.
Files added:
src/main/java/ca/etsmtl/taf/config/JpaAuditingConfig.java
src/main/java/ca/etsmtl/taf/security/MongoSecurityConfig.java
src/main/resources/application-mongo.yml
src/main/resources/application-sql.yml
Files modified:
src/main/java/ca/etsmtl/taf/TestAutomationFrameworkApplication.java
src/main/java/ca/etsmtl/taf/config/EnvConfig.java
src/main/java/ca/etsmtl/taf/config/SQLConfig.java
src/main/java/ca/etsmtl/taf/controller/ApiBddController.java
src/main/java/ca/etsmtl/taf/controller/AuthController.java
src/main/java/ca/etsmtl/taf/controller/TestController.java
src/main/java/ca/etsmtl/taf/repository/ApiBddJmeterRepository.java
src/main/java/ca/etsmtl/taf/repository/ProjectRepository.java
src/main/java/ca/etsmtl/taf/repository/RoleRepository.java
src/main/java/ca/etsmtl/taf/repository/TestRepository.java
src/main/java/ca/etsmtl/taf/repository/UserRepository.java
src/main/java/ca/etsmtl/taf/security/WebSecurityConfig.java
src/main/java/ca/etsmtl/taf/security/services/UserDetailsServiceImpl.java
src/main/java/ca/etsmtl/taf/service/ApiBddService.java
src/main/resources/application.properties
.gitignore (added explanations + protections for env files)
Expected benefits:
The backend now starts cleanly using MongoDB with:
-No SQL errors
-No datasource initialization
-No login redirections
The frontend will be able to call backend routes on port 8086 through a Codespace URL.
The 2nd Commit in this Pull Request: Dashboard fixes, Codespaces proxy, and mock data
This commit adds support for running the Équipe 5 (Test Result Dashboard) frontend + backend in GitHub Codespaces and provides full dashboard mock data (63 days of tests) for local development.
New files:
Modified files: