Fix dead links

Author: leeyi45

docs/src/modules/1-getting-started/4-cheat.md

@@ -120,7 +120,7 @@ Both the `--tsc` and `--lint` options can be used togther to run `tsc` and ESLin
 #### NOTES
 
 - Running `yarn lint --fix` will fix any automatically fixable errors
-- The test command has several options. Refer to [this](../4-advanced/testing) page for more information.
+- The test command has several options. Refer to [this](../4-testing/4-unit) page for more information.
 
 ## Root Repository Commands
 

docs/src/modules/1-getting-started/5-faq.md

@@ -15,7 +15,7 @@ title: FAQ
 > 1. `bundle/**/*.ts` is where we store all logical functions
 > 2. `tabs/**/*.tsx` is where we use all the react and jsx which will be shown in the frontend
 
-A brief overview of the current infrastructure is explained [here](../4-advanced/flow/flow). However, I would like to explain in more detail how the `bundle` and `tab` interacts with `js-slang` and `cadet-frontend` respectively.
+A brief overview of the current infrastructure is explained [here](../5-advanced/flow/flow). However, I would like to explain in more detail how the `bundle` and `tab` interacts with `js-slang` and `cadet-frontend` respectively.
 
 Firstly, a `bundle` is defined as the suite of functions that are provided by the module. More specifically, what we mean by this is that the bundle will provide all the functions and constants that are intended to be available for use by the cadet when programming in the Source language.
 

docs/src/modules/2-bundle/3-editing.md

@@ -79,4 +79,4 @@ instead of implementing your own versions of them.
 
 ## Adding Unit Tests
 
-Where possible, you should add unit tests to your bundle. Refer to [this](/modules/4-advanced/testing) page for instructions.
+Where possible, you should add unit tests to your bundle. Refer to [this](/modules/4-testing/) page for instructions.

docs/src/modules/3-tabs/4-context/4-context.md

@@ -1,6 +1,6 @@
 # Working with Module Contexts
 
-Module contexts are a way to pass information between bundles and tabs. A more in-depth introduction to module contexts can be found [here](/modules/4-advanced/context).
+Module contexts are a way to pass information between bundles and tabs. A more in-depth introduction to module contexts can be found [here](/modules/5-advanced/context).
 
 A module's tabs are always loaded after its bundle, and only if its bundle was imported by the Source program.
 This means that it is safe to assume that a module's context object has been initialized (if there is code in the bundle that does so)

docs/src/modules/4-testing/index.md

@@ -1,3 +1,10 @@
 ---
 title: Dev and Testing
 ---
+
+There are several ways you can test your bundles and tabs during development. This section lists those methods.
+
+- [Running on Desktop](./1-desktop)
+- [With the Devserver](./2-devserver/2-devserver)
+- [With the frontend](./3-frontend)
+- [Unit Testing](./4-unit)

lib/repotools/src/utils.ts

@@ -45,34 +45,6 @@ export function findSeverity<T>(items: T[], mapper: (each: T) => Severity): Seve
   return output;
 }
 
-/*
-export function processSeverities(items: { severity: Severity }[]) {
-  return findSeverity(items, ({ severity }) => severity);
-}
-
-type CollatedResult<T> = {
-  [k: `bundle-${string}`]: T
-} | {
-  [k: `tab-${string}`]: T
-};
-
-export function collateResults<T extends { bundle: ResolvedBundle } | { tab: ResolvedTab }>(results: T[]) {
-  return results.reduce<CollatedResult<T>>((res, each) => {
-    if ('bundle' in each) {
-      return {
-        ...res,
-        [`bundle-${each.bundle.name}`]: each
-      };
-    }
-
-    return {
-      ...res,
-      [`tab-${each.tab.name}`]: each
-    };
-  }, {});
-}
-*/
-
 export const divideAndRound = (n: number, divisor: number) => (n / divisor).toFixed(2);
 
 export function isNodeError(error: unknown): error is NodeJS.ErrnoException {