From 00b704481d612ca67e88cef3abc2205ec05bdb1e Mon Sep 17 00:00:00 2001 From: Steven Dalamaras Date: Sun, 29 Mar 2026 14:40:56 +1000 Subject: [PATCH 1/3] docs: add Gurwinder's contributions for ai effort --- .../Task Effort Prediction/ai-effort-into.mdx | 19 +++++ .../effort-prediction-doc.md | 83 +++++++++++++++++++ 2 files changed, 102 insertions(+) create mode 100644 src/content/docs/Products/OnTrack/Projects/Task Effort Prediction/ai-effort-into.mdx create mode 100644 src/content/docs/Products/OnTrack/Projects/Task Effort Prediction/effort-prediction-doc.md diff --git a/src/content/docs/Products/OnTrack/Projects/Task Effort Prediction/ai-effort-into.mdx b/src/content/docs/Products/OnTrack/Projects/Task Effort Prediction/ai-effort-into.mdx new file mode 100644 index 00000000..97cef9fb --- /dev/null +++ b/src/content/docs/Products/OnTrack/Projects/Task Effort Prediction/ai-effort-into.mdx @@ -0,0 +1,19 @@ +--- +title: "Task Effort Prediction with AI" +sidebar: + label: "Executive Summary" +--- + +## Executive Summary + +This feature project aims to develop a system, including a machine learning +model for predicting the amount of effort required for students to complete +academic tasks. By analysing task metadata and extracting key information from +task sheets, the system will generate consistent, data-driven workload +estimates for students based on metrics derived from the OnTrack learning +management system. + +## Objective + +This project aims to create a + diff --git a/src/content/docs/Products/OnTrack/Projects/Task Effort Prediction/effort-prediction-doc.md b/src/content/docs/Products/OnTrack/Projects/Task Effort Prediction/effort-prediction-doc.md new file mode 100644 index 00000000..a34d9080 --- /dev/null +++ b/src/content/docs/Products/OnTrack/Projects/Task Effort Prediction/effort-prediction-doc.md @@ -0,0 +1,83 @@ +--- +title: Design Document - AI-Based Effort Prediction Feature +--- + +## 1. Introduction +The AI‑based Effort Prediction feature is designed to support students and staff by estimating assignment workload and effort. This integrates machine learning regression models into OnTrack’s backend, enabling predictive insights that can be consumed by the frontend. The goal is to enhance student success by providing data‑driven guidance while ensuring scalability, reproducibility, and transparency. + +--- + +## 2. Setup and Environment +- **Local Setup:** Project cloned and configured in Ruby on Rails backend. +- **Environment Issues Resolved:** Addressed Docker networking, dependency mismatches, and Rails to TorchServe connectivity. +- **Outcome:** Stable local environment established for model serving and backend integration. + +--- + +## 3. Prototype and Service Agent Design +- **Prototype:** Prepared an early prototype of the service agent to test regression model predictions. +- **Integration:** Later integrated the prototype into the Rails backend, ensuring predictions could be requested via API. +- **Communication:** Progress updates shared with team members to keep development aligned and transparent. + +--- + +## 4. Backend Implementation +- **Model Serving:** + - Evaluated ML frameworks (Hugging Face, TensorFlow, PyTorch). + - Selected TorchServe for scalability and production readiness. +- **Service Agent:** + - Designed to handle regression model requests. + - Provides prediction results in JSON format for frontend consumption. +- **Database Interaction:** + - Logs prediction requests and outputs for reproducibility and auditing. + +--- + +## 5. Testing Strategy +### Backend Tests +- Successful prediction request and response. +- Invalid input handling. +- Container connectivity validation (Rails to TorchServe). + +### Model Training and Validation +- **Training:** Regression models will be trained on labelled effort data to capture workload patterns. +- **Validation:** Accuracy of predictions will be validated against held‑out test data. +- **Outcome:** Ensures the model generalises well to unseen inputs and provides reliable effort estimates. + +### Peer Review Testing +- Validate Dockerfile changes. + +--- + +## 6. Error Handling & Validation +- **Input Validation:** Ensure prediction requests include valid parameters. +- **Exception Handling:** Backend logs errors and returns user‑friendly messages. +- **Reproducibility:** Planned documentation of integration steps and challenges to enable teammates to replicate and test the solution. + +--- + +## 7. Deployment Plan +- **Pre‑Deployment:** + - Test TorchServe integration locally. + - Review code for reproducibility and maintainability. +- **Deployment Steps:** + - Deploy Rails service agent with TorchServe container. + - Expose API endpoint for frontend integration. +- **Post‑Deployment:** + - Monitor prediction accuracy and performance. + - Gather feedback from staff and students. +- **Rollback Plan:** + - Revert to baseline backend without prediction agent if issues arise. + +--- + +## 8. Outstanding Documentation (Planned) +- Step‑by‑step guide for setting up TorchServe with Rails. +- Challenges faced during environment setup and integration. +- Reproducible testing scripts for backend validation. +- Screenshots of prediction API requests and responses. + +--- + +## 9. Conclusion +The AI‑based Effort Prediction feature enhances OnTrack by providing predictive insights into assignment workload. While the prototype and integration have been completed, further documentation of implementation steps and challenges is planned to ensure reproducibility, maintainability, and long‑term success. From fc55f3bf6efb13e417336e7f045dd999e1cb11f1 Mon Sep 17 00:00:00 2001 From: officialid130-13e13 Date: Sat, 28 Mar 2026 10:24:36 +0530 Subject: [PATCH 2/3] Added design document for AI based effort prediction feature and minor improvements --- .../effort-prediction-doc.md | 83 +++++++++++++++++++ .../group-task-submission-doc.md | 2 +- .../Projects/Staff Grant Extension/DESIGN.md | 2 +- .../Templates/srs-template.md | 4 +- .../git-contributions-guide.mdx | 1 + .../quality-assurance-overview.md | 7 +- 6 files changed, 92 insertions(+), 7 deletions(-) create mode 100644 src/content/docs/Products/OnTrack/Projects/Effort Prediction/effort-prediction-doc.md diff --git a/src/content/docs/Products/OnTrack/Projects/Effort Prediction/effort-prediction-doc.md b/src/content/docs/Products/OnTrack/Projects/Effort Prediction/effort-prediction-doc.md new file mode 100644 index 00000000..a34d9080 --- /dev/null +++ b/src/content/docs/Products/OnTrack/Projects/Effort Prediction/effort-prediction-doc.md @@ -0,0 +1,83 @@ +--- +title: Design Document - AI-Based Effort Prediction Feature +--- + +## 1. Introduction +The AI‑based Effort Prediction feature is designed to support students and staff by estimating assignment workload and effort. This integrates machine learning regression models into OnTrack’s backend, enabling predictive insights that can be consumed by the frontend. The goal is to enhance student success by providing data‑driven guidance while ensuring scalability, reproducibility, and transparency. + +--- + +## 2. Setup and Environment +- **Local Setup:** Project cloned and configured in Ruby on Rails backend. +- **Environment Issues Resolved:** Addressed Docker networking, dependency mismatches, and Rails to TorchServe connectivity. +- **Outcome:** Stable local environment established for model serving and backend integration. + +--- + +## 3. Prototype and Service Agent Design +- **Prototype:** Prepared an early prototype of the service agent to test regression model predictions. +- **Integration:** Later integrated the prototype into the Rails backend, ensuring predictions could be requested via API. +- **Communication:** Progress updates shared with team members to keep development aligned and transparent. + +--- + +## 4. Backend Implementation +- **Model Serving:** + - Evaluated ML frameworks (Hugging Face, TensorFlow, PyTorch). + - Selected TorchServe for scalability and production readiness. +- **Service Agent:** + - Designed to handle regression model requests. + - Provides prediction results in JSON format for frontend consumption. +- **Database Interaction:** + - Logs prediction requests and outputs for reproducibility and auditing. + +--- + +## 5. Testing Strategy +### Backend Tests +- Successful prediction request and response. +- Invalid input handling. +- Container connectivity validation (Rails to TorchServe). + +### Model Training and Validation +- **Training:** Regression models will be trained on labelled effort data to capture workload patterns. +- **Validation:** Accuracy of predictions will be validated against held‑out test data. +- **Outcome:** Ensures the model generalises well to unseen inputs and provides reliable effort estimates. + +### Peer Review Testing +- Validate Dockerfile changes. + +--- + +## 6. Error Handling & Validation +- **Input Validation:** Ensure prediction requests include valid parameters. +- **Exception Handling:** Backend logs errors and returns user‑friendly messages. +- **Reproducibility:** Planned documentation of integration steps and challenges to enable teammates to replicate and test the solution. + +--- + +## 7. Deployment Plan +- **Pre‑Deployment:** + - Test TorchServe integration locally. + - Review code for reproducibility and maintainability. +- **Deployment Steps:** + - Deploy Rails service agent with TorchServe container. + - Expose API endpoint for frontend integration. +- **Post‑Deployment:** + - Monitor prediction accuracy and performance. + - Gather feedback from staff and students. +- **Rollback Plan:** + - Revert to baseline backend without prediction agent if issues arise. + +--- + +## 8. Outstanding Documentation (Planned) +- Step‑by‑step guide for setting up TorchServe with Rails. +- Challenges faced during environment setup and integration. +- Reproducible testing scripts for backend validation. +- Screenshots of prediction API requests and responses. + +--- + +## 9. Conclusion +The AI‑based Effort Prediction feature enhances OnTrack by providing predictive insights into assignment workload. While the prototype and integration have been completed, further documentation of implementation steps and challenges is planned to ensure reproducibility, maintainability, and long‑term success. diff --git a/src/content/docs/Products/OnTrack/Projects/Group Task Submission/group-task-submission-doc.md b/src/content/docs/Products/OnTrack/Projects/Group Task Submission/group-task-submission-doc.md index 78730c6a..0ef17646 100644 --- a/src/content/docs/Products/OnTrack/Projects/Group Task Submission/group-task-submission-doc.md +++ b/src/content/docs/Products/OnTrack/Projects/Group Task Submission/group-task-submission-doc.md @@ -1,5 +1,5 @@ --- -title: Design a way to improve the group Task submission - Documen +title: Design a way to improve the group Task submission - Document --- ## Solution 1: Selecting Students Who Can Submit diff --git a/src/content/docs/Products/OnTrack/Projects/Staff Grant Extension/DESIGN.md b/src/content/docs/Products/OnTrack/Projects/Staff Grant Extension/DESIGN.md index cb2e044f..919f76cc 100644 --- a/src/content/docs/Products/OnTrack/Projects/Staff Grant Extension/DESIGN.md +++ b/src/content/docs/Products/OnTrack/Projects/Staff Grant Extension/DESIGN.md @@ -1,5 +1,5 @@ --- -title: Design Document:OnTrack - Staff Grant Extension Featur +title: Design Document:OnTrack - Staff Grant Extension Feature --- ## 1-Introduction diff --git a/src/content/docs/Resources/Quality Assurance/Templates/srs-template.md b/src/content/docs/Resources/Quality Assurance/Templates/srs-template.md index 76269ead..8244a50f 100644 --- a/src/content/docs/Resources/Quality Assurance/Templates/srs-template.md +++ b/src/content/docs/Resources/Quality Assurance/Templates/srs-template.md @@ -16,13 +16,13 @@ sidebar: ### 1.5 Definitions and Acronyms -## Overall Description +## 2. Overall Description ### 2.1 User Needs ### 2.2 Assumptions and Dependencies -## System Features and Requirements +## 3. System Features and Requirements ### 3.1 Functional Requirements diff --git a/src/content/docs/Resources/Quality Assurance/git-contributions-guide.mdx b/src/content/docs/Resources/Quality Assurance/git-contributions-guide.mdx index 9db79973..cb30557d 100644 --- a/src/content/docs/Resources/Quality Assurance/git-contributions-guide.mdx +++ b/src/content/docs/Resources/Quality Assurance/git-contributions-guide.mdx @@ -7,6 +7,7 @@ title: Git Contribution Guide - [Contributing to Repositories: How To](#contributing-to-repositories-how-to) - [Branching Guidelines](#branching-guidelines) - [Commit Guidelines](#commit-guidelines) +- [Commit Message Guidelines](#commit-message-guidelines) - [Code Review Guidelines](#code-review-guidelines) - [Git Workflow Summary](#git-workflow-summary) diff --git a/src/content/docs/Resources/Quality Assurance/quality-assurance-overview.md b/src/content/docs/Resources/Quality Assurance/quality-assurance-overview.md index 63eb6eb0..f0f0b509 100644 --- a/src/content/docs/Resources/Quality Assurance/quality-assurance-overview.md +++ b/src/content/docs/Resources/Quality Assurance/quality-assurance-overview.md @@ -27,7 +27,7 @@ requests. - [Contributing to Repositories: How To](/resources/quality-assurance/git-contributions-guide#contributing-to-repositories-how-to) - [Branching Guidelines](/resources/quality-assurance/git-contributions-guide#branching-guidelines) - [Commit Guidelines](/resources/quality-assurance/git-contributions-guide#commit-guidelines) -- [Commit Message Format](/resources/quality-assurance/git-contributions-guide#message-format) +- [Commit Message Guidelines](/resources/quality-assurance/git-contributions-guide#commit-message-guidelines) - [Code Review Guidelines](/resources/quality-assurance/git-contributions-guide#code-review-guidelines) - [Git Workflow Summary](/resources/quality-assurance/git-contributions-guide#git-workflow-summary) @@ -45,8 +45,9 @@ development process. - [Epics and User Stories](/resources/quality-assurance/testing-and-dev#epics-and-user-stories) - [Software Requirements Specification Document](/resources/quality-assurance/testing-and-dev#software-requirements-specification-document) - [Testing and Development](/resources/quality-assurance/testing-and-dev#testing-and-development) - - [Test Strategy](/resources/quality-assurance/testing-and-dev#test-strategy) + - [Testing Templates](/resources/quality-assurance/testing-and-dev#testing-templates) - [Test Plans](/resources/quality-assurance/testing-and-dev#making-a-test-plan) + - [Test Strategy](/resources/quality-assurance/testing-and-dev#test-strategy) - [Testing Tools](/resources/quality-assurance/testing-and-dev#testing-tools) - [Test Driven Development](/resources/quality-assurance/testing-and-dev#test-driven-development) - - [Testing Templates](/resources/quality-assurance/testing-and-dev#testing-templates) + From 0614ffcec4b89b236e6f79c4ae0afef3a3c9b15d Mon Sep 17 00:00:00 2001 From: Steven Dalamaras Date: Fri, 3 Apr 2026 14:35:30 +1000 Subject: [PATCH 3/3] docs: tighten scope of feature branch PR docs: remove duplicate doc docs: change md to mdx files --- ...docker-documentation-research-t1-2022.mdx} | 0 ...s-software-requirements-specification.mdx} | 0 .../effort-prediction-doc.md | 83 ------------------- .../group-task-submission-doc.md | 2 +- .../Projects/Staff Grant Extension/DESIGN.md | 2 +- .../Templates/srs-template.md | 4 +- .../git-contributions-guide.mdx | 1 - .../quality-assurance-overview.md | 7 +- ...testing-and-dev.md => testing-and-dev.mdx} | 0 9 files changed, 7 insertions(+), 92 deletions(-) rename src/content/docs/Products/OnTrack/Documentation/Jupyter Notebook/{docker-documentation-research-t1-2022.md => docker-documentation-research-t1-2022.mdx} (100%) rename src/content/docs/Products/OnTrack/Documentation/Jupyter Notebook/{prototype-srs-software-requirements-specification.md => prototype-srs-software-requirements-specification.mdx} (100%) delete mode 100644 src/content/docs/Products/OnTrack/Projects/Effort Prediction/effort-prediction-doc.md rename src/content/docs/Resources/Quality Assurance/{testing-and-dev.md => testing-and-dev.mdx} (100%) diff --git a/src/content/docs/Products/OnTrack/Documentation/Jupyter Notebook/docker-documentation-research-t1-2022.md b/src/content/docs/Products/OnTrack/Documentation/Jupyter Notebook/docker-documentation-research-t1-2022.mdx similarity index 100% rename from src/content/docs/Products/OnTrack/Documentation/Jupyter Notebook/docker-documentation-research-t1-2022.md rename to src/content/docs/Products/OnTrack/Documentation/Jupyter Notebook/docker-documentation-research-t1-2022.mdx diff --git a/src/content/docs/Products/OnTrack/Documentation/Jupyter Notebook/prototype-srs-software-requirements-specification.md b/src/content/docs/Products/OnTrack/Documentation/Jupyter Notebook/prototype-srs-software-requirements-specification.mdx similarity index 100% rename from src/content/docs/Products/OnTrack/Documentation/Jupyter Notebook/prototype-srs-software-requirements-specification.md rename to src/content/docs/Products/OnTrack/Documentation/Jupyter Notebook/prototype-srs-software-requirements-specification.mdx diff --git a/src/content/docs/Products/OnTrack/Projects/Effort Prediction/effort-prediction-doc.md b/src/content/docs/Products/OnTrack/Projects/Effort Prediction/effort-prediction-doc.md deleted file mode 100644 index a34d9080..00000000 --- a/src/content/docs/Products/OnTrack/Projects/Effort Prediction/effort-prediction-doc.md +++ /dev/null @@ -1,83 +0,0 @@ ---- -title: Design Document - AI-Based Effort Prediction Feature ---- - -## 1. Introduction -The AI‑based Effort Prediction feature is designed to support students and staff by estimating assignment workload and effort. This integrates machine learning regression models into OnTrack’s backend, enabling predictive insights that can be consumed by the frontend. The goal is to enhance student success by providing data‑driven guidance while ensuring scalability, reproducibility, and transparency. - ---- - -## 2. Setup and Environment -- **Local Setup:** Project cloned and configured in Ruby on Rails backend. -- **Environment Issues Resolved:** Addressed Docker networking, dependency mismatches, and Rails to TorchServe connectivity. -- **Outcome:** Stable local environment established for model serving and backend integration. - ---- - -## 3. Prototype and Service Agent Design -- **Prototype:** Prepared an early prototype of the service agent to test regression model predictions. -- **Integration:** Later integrated the prototype into the Rails backend, ensuring predictions could be requested via API. -- **Communication:** Progress updates shared with team members to keep development aligned and transparent. - ---- - -## 4. Backend Implementation -- **Model Serving:** - - Evaluated ML frameworks (Hugging Face, TensorFlow, PyTorch). - - Selected TorchServe for scalability and production readiness. -- **Service Agent:** - - Designed to handle regression model requests. - - Provides prediction results in JSON format for frontend consumption. -- **Database Interaction:** - - Logs prediction requests and outputs for reproducibility and auditing. - ---- - -## 5. Testing Strategy -### Backend Tests -- Successful prediction request and response. -- Invalid input handling. -- Container connectivity validation (Rails to TorchServe). - -### Model Training and Validation -- **Training:** Regression models will be trained on labelled effort data to capture workload patterns. -- **Validation:** Accuracy of predictions will be validated against held‑out test data. -- **Outcome:** Ensures the model generalises well to unseen inputs and provides reliable effort estimates. - -### Peer Review Testing -- Validate Dockerfile changes. - ---- - -## 6. Error Handling & Validation -- **Input Validation:** Ensure prediction requests include valid parameters. -- **Exception Handling:** Backend logs errors and returns user‑friendly messages. -- **Reproducibility:** Planned documentation of integration steps and challenges to enable teammates to replicate and test the solution. - ---- - -## 7. Deployment Plan -- **Pre‑Deployment:** - - Test TorchServe integration locally. - - Review code for reproducibility and maintainability. -- **Deployment Steps:** - - Deploy Rails service agent with TorchServe container. - - Expose API endpoint for frontend integration. -- **Post‑Deployment:** - - Monitor prediction accuracy and performance. - - Gather feedback from staff and students. -- **Rollback Plan:** - - Revert to baseline backend without prediction agent if issues arise. - ---- - -## 8. Outstanding Documentation (Planned) -- Step‑by‑step guide for setting up TorchServe with Rails. -- Challenges faced during environment setup and integration. -- Reproducible testing scripts for backend validation. -- Screenshots of prediction API requests and responses. - ---- - -## 9. Conclusion -The AI‑based Effort Prediction feature enhances OnTrack by providing predictive insights into assignment workload. While the prototype and integration have been completed, further documentation of implementation steps and challenges is planned to ensure reproducibility, maintainability, and long‑term success. diff --git a/src/content/docs/Products/OnTrack/Projects/Group Task Submission/group-task-submission-doc.md b/src/content/docs/Products/OnTrack/Projects/Group Task Submission/group-task-submission-doc.md index 0ef17646..78730c6a 100644 --- a/src/content/docs/Products/OnTrack/Projects/Group Task Submission/group-task-submission-doc.md +++ b/src/content/docs/Products/OnTrack/Projects/Group Task Submission/group-task-submission-doc.md @@ -1,5 +1,5 @@ --- -title: Design a way to improve the group Task submission - Document +title: Design a way to improve the group Task submission - Documen --- ## Solution 1: Selecting Students Who Can Submit diff --git a/src/content/docs/Products/OnTrack/Projects/Staff Grant Extension/DESIGN.md b/src/content/docs/Products/OnTrack/Projects/Staff Grant Extension/DESIGN.md index 919f76cc..cb2e044f 100644 --- a/src/content/docs/Products/OnTrack/Projects/Staff Grant Extension/DESIGN.md +++ b/src/content/docs/Products/OnTrack/Projects/Staff Grant Extension/DESIGN.md @@ -1,5 +1,5 @@ --- -title: Design Document:OnTrack - Staff Grant Extension Feature +title: Design Document:OnTrack - Staff Grant Extension Featur --- ## 1-Introduction diff --git a/src/content/docs/Resources/Quality Assurance/Templates/srs-template.md b/src/content/docs/Resources/Quality Assurance/Templates/srs-template.md index 8244a50f..76269ead 100644 --- a/src/content/docs/Resources/Quality Assurance/Templates/srs-template.md +++ b/src/content/docs/Resources/Quality Assurance/Templates/srs-template.md @@ -16,13 +16,13 @@ sidebar: ### 1.5 Definitions and Acronyms -## 2. Overall Description +## Overall Description ### 2.1 User Needs ### 2.2 Assumptions and Dependencies -## 3. System Features and Requirements +## System Features and Requirements ### 3.1 Functional Requirements diff --git a/src/content/docs/Resources/Quality Assurance/git-contributions-guide.mdx b/src/content/docs/Resources/Quality Assurance/git-contributions-guide.mdx index cb30557d..9db79973 100644 --- a/src/content/docs/Resources/Quality Assurance/git-contributions-guide.mdx +++ b/src/content/docs/Resources/Quality Assurance/git-contributions-guide.mdx @@ -7,7 +7,6 @@ title: Git Contribution Guide - [Contributing to Repositories: How To](#contributing-to-repositories-how-to) - [Branching Guidelines](#branching-guidelines) - [Commit Guidelines](#commit-guidelines) -- [Commit Message Guidelines](#commit-message-guidelines) - [Code Review Guidelines](#code-review-guidelines) - [Git Workflow Summary](#git-workflow-summary) diff --git a/src/content/docs/Resources/Quality Assurance/quality-assurance-overview.md b/src/content/docs/Resources/Quality Assurance/quality-assurance-overview.md index f0f0b509..63eb6eb0 100644 --- a/src/content/docs/Resources/Quality Assurance/quality-assurance-overview.md +++ b/src/content/docs/Resources/Quality Assurance/quality-assurance-overview.md @@ -27,7 +27,7 @@ requests. - [Contributing to Repositories: How To](/resources/quality-assurance/git-contributions-guide#contributing-to-repositories-how-to) - [Branching Guidelines](/resources/quality-assurance/git-contributions-guide#branching-guidelines) - [Commit Guidelines](/resources/quality-assurance/git-contributions-guide#commit-guidelines) -- [Commit Message Guidelines](/resources/quality-assurance/git-contributions-guide#commit-message-guidelines) +- [Commit Message Format](/resources/quality-assurance/git-contributions-guide#message-format) - [Code Review Guidelines](/resources/quality-assurance/git-contributions-guide#code-review-guidelines) - [Git Workflow Summary](/resources/quality-assurance/git-contributions-guide#git-workflow-summary) @@ -45,9 +45,8 @@ development process. - [Epics and User Stories](/resources/quality-assurance/testing-and-dev#epics-and-user-stories) - [Software Requirements Specification Document](/resources/quality-assurance/testing-and-dev#software-requirements-specification-document) - [Testing and Development](/resources/quality-assurance/testing-and-dev#testing-and-development) - - [Testing Templates](/resources/quality-assurance/testing-and-dev#testing-templates) - - [Test Plans](/resources/quality-assurance/testing-and-dev#making-a-test-plan) - [Test Strategy](/resources/quality-assurance/testing-and-dev#test-strategy) + - [Test Plans](/resources/quality-assurance/testing-and-dev#making-a-test-plan) - [Testing Tools](/resources/quality-assurance/testing-and-dev#testing-tools) - [Test Driven Development](/resources/quality-assurance/testing-and-dev#test-driven-development) - + - [Testing Templates](/resources/quality-assurance/testing-and-dev#testing-templates) diff --git a/src/content/docs/Resources/Quality Assurance/testing-and-dev.md b/src/content/docs/Resources/Quality Assurance/testing-and-dev.mdx similarity index 100% rename from src/content/docs/Resources/Quality Assurance/testing-and-dev.md rename to src/content/docs/Resources/Quality Assurance/testing-and-dev.mdx