Skip to content

Commit c69d16b

Browse files
Barb CutlerBarb Cutler
Barb Cutler
authored and
Barb Cutler
committed
add category to multiple pages in the ci section of outline
1 parent 2f663db commit c69d16b

9 files changed

+10
-2
lines changed

_docs/developer/testing/autograding_integration_tests.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Autograding Tests
3-
category: Developer
3+
category: Developer > Development Instructions > Continuous Integration Testing
44
---
55

66
_NOTE: Currently, these tests can only be run from within Vagrant._

_docs/developer/testing/cypress.md

+1
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: End-to-End testing with Cypress
3+
category: Developer > Development Instructions > Continuous Integration Testing
34
---
45

56
The _End-to-End Testing_ (e2e) suite utilizes [Cypress](https://www.cypress.io/),

_docs/developer/testing/external_contributors.md

+1
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: External Contributors
3+
category: Developer > Development Instructions > Continuous Integration Testing
34
---
45

56
To run all Submitty workflows on a forked repository, you must manually trigger the workflow. This is because GitHub Actions do not run on forked repositories by default. One of the people in the Submitty organization must manually trigger the workflow for you. To avoid this, you can trust the workflow in your forked repository. This will allow GitHub Actions to run on your forked repository without manual intervention.

_docs/developer/testing/github_actions.md

+1
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: GitHub Actions
3+
category: Developer > Development Instructions > Continuous Integration Testing
34
---
45

56
We utilize [GitHub actions](https://docs.github.com/en/actions) to enable *continuous integration*

_docs/developer/testing/index.md

+2-1
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
2-
title: Testing
2+
title: Continuous Integration Testing
3+
category: Developer > Development Instructions
34
---
45

56
To verify expected behavior of Submitty, we use

_docs/developer/testing/install_php.md

+1
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: Install PHP
3+
category: Developer > Development Instructions > Continuous Integration Testing
34
---
45

56
In order to run the PHP Linter, Static Analysis, and PHPUnit tests locally

_docs/developer/testing/linting_static_analysis.md

+1
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: Linting / Static Analysis
3+
category: Developer > Development Instructions > Continuous Integration Testing
34
---
45

56
To ensure the [Coding Standards](/developer/coding_style_guide) of Submitty, we use a mixture

_docs/developer/testing/php_unit_tests.md

+1
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: PHP Unit Tests
3+
category: Developer > Development Instructions > Continuous Integration Testing
34
---
45

56
To validate the unit behavior of the site code, we utilize

_docs/developer/testing/python_unit_tests.md

+1
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: Python Unit Tests
3+
category: Developer > Development Instructions > Continuous Integration Testing
34
---
45

56
The following Python modules of Submitty are unit tested:

0 commit comments

Comments
 (0)