diff --git a/testingWithJest/.gitignore b/testingWithJest/.gitignore
new file mode 100644
index 00000000..26f231a4
--- /dev/null
+++ b/testingWithJest/.gitignore
@@ -0,0 +1,135 @@
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+lerna-debug.log*
+.pnpm-debug.log*
+# editor back up files
+*~
+
+# Diagnostic reports (https://nodejs.org/api/report.html)
+report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json
+
+# Runtime data
+pids
+*.pid
+*.seed
+*.pid.lock
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Coverage directory used by tools like istanbul
+coverage
+*.lcov
+
+# nyc test coverage
+.nyc_output
+
+# Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)
+.grunt
+
+# Bower dependency directory (https://bower.io/)
+bower_components
+
+# node-waf configuration
+.lock-wscript
+
+# Compiled binary addons (https://nodejs.org/api/addons.html)
+build/Release
+
+# Dependency directories
+node_modules/
+jspm_packages/
+
+# my script folder
+script/
+
+# Snowpack dependency directory (https://snowpack.dev/)
+web_modules/
+
+# TypeScript cache
+*.tsbuildinfo
+
+# Optional npm cache directory
+.npm
+
+# Optional eslint cache
+.eslintcache
+
+# Optional stylelint cache
+.stylelintcache
+
+# Microbundle cache
+.rpt2_cache/
+.rts2_cache_cjs/
+.rts2_cache_es/
+.rts2_cache_umd/
+
+# Optional REPL history
+.node_repl_history
+
+# Output of 'npm pack'
+*.tgz
+
+# Yarn Integrity file
+.yarn-integrity
+
+# dotenv environment variable files
+.env
+.env.development.local
+.env.test.local
+.env.production.local
+.env.local
+
+# parcel-bundler cache (https://parceljs.org/)
+.cache
+.parcel-cache
+
+# Next.js build output
+.next
+out
+
+# Nuxt.js build / generate output
+.nuxt
+dist
+
+# Gatsby files
+.cache/
+# Comment in the public line in if your project uses Gatsby and not Next.js
+# https://nextjs.org/blog/next-9-1#public-directory-support
+# public
+
+# vuepress build output
+.vuepress/dist
+
+# vuepress v2.x temp and cache directory
+.temp
+.cache
+
+# Docusaurus cache and generated files
+.docusaurus
+
+# Serverless directories
+.serverless/
+
+# FuseBox cache
+.fusebox/
+
+# DynamoDB Local files
+.dynamodb/
+
+# TernJS port file
+.tern-port
+
+# Stores VSCode versions used for testing VSCode extensions
+.vscode-test
+
+# yarn v2
+.yarn/cache
+.yarn/unplugged
+.yarn/build-state.yml
+.yarn/install-state.gz
+.pnp.*
\ No newline at end of file
diff --git a/testingWithJest/README.md b/testingWithJest/README.md
new file mode 100644
index 00000000..1c3b8648
--- /dev/null
+++ b/testingWithJest/README.md
@@ -0,0 +1,316 @@
+author: Tony Beaumont
+summary: Workshop on Jest for testing
+id: docs
+categories: digital
+environments: Web
+status: Published
+feedback link: mailto:a.j.beaumont@aston.ac.uk
+
+
+# Testing with Jest
+
+## Welcome
+
+This workshop looks at writing unit tests in Jest.
+
+### Introduction
+
+This workshop goes with Sprint 3 of Structuring and testing data (See [https://programming.codeyourfuture.io/structuring-data/sprints/3/](https://programming.codeyourfuture.io/structuring-data/sprints/3/)
+
+
+> aside positive
+> ### Important
+>
+> You should have completed the prep for this sprint from [https://programming.codeyourfuture.io/structuring-data/sprints/3/prep/](https://programming.codeyourfuture.io/structuring-data/sprints/3/prep/)
+
+### What you should already know
+
+As a trainee you should:
+* be able to write Javascript functions
+* be able to write Jest unit tests as described in the prep.
+
+### What you'll learn
+
+* How to write unit tests
+* How to design tests
+* How to think about the relationship between tests and your code
+* How to do Test Driven Development
+
+### What you'll need
+
+You will need a computer with the latest versions of this software installed:
+
+* VS Code
+* node ([https://nodejs.org/en/download/package-manager](https://nodejs.org/en/download/package-manager)
+* npm
+
+These are the versions I have installed:
+```console
+$ node --version
+v21.2.0
+$ npm --version
+10.9.0
+```
+
+
+### What you'll do
+
+The following pages will take you through all the steps of the workshop.
+
+* Clone a copy of the workshop from [https://github.com/beaumoaj/jestWorkshop](https://github.com/beaumoaj/jestWorkshop)
+* Run the demo
+* Run the existing tests
+* Read the specification for the `makeAppointment` function
+* Write tests and modify to the code to ensure `makeAppointment` meets the specification.
+
+## Where to find the workshop
+
+1. Open the workshop instructions which can be found here: [https://beaumoaj.github.io/jestWorkshop/#0](https://beaumoaj.github.io/jestWorkshop/#0)
+1. You should `fork` and then `clone` the workshop repository which you will find here: [https://github.com/beaumoaj/jestWorkshop](https://github.com/beaumoaj/jestWorkshop). Note this repository is currently private, I will make it public at the start of the workshop for you to fork it.
+
+## Exploring the workshop project
+
+Once you have forked the repository and cloned a copy to your computer, open the folder in VS Code. It should look like this:
+
+
+
+This project contains the following files:
+
+* `day.js` which provides the functionality to store appointments during a given day.
+* `dayDemo.js` contains brief demo of how to use the existing code in `day.js`.
+* `day.test.js` contains the beginnings of a set of unit tests for `day.js`.
+
+### Running the code
+
+1. Open the `package.json` first and look at the `dependencies` (you will see `jest`) and look at the `scripts` - you will see `demo` and `test`. The `scripts` definitions allow you to run two actions, `demo` and `test` (don't run them yet).
+1. Open the file called `dayTest.js`. It constains the following code:
+ ```javascript
+ const {
+ setUpDay,
+ makeAppointment,
+ getAppointment,
+ getLengthOfDay,
+ getFirstAppointmentTime,
+ getLastAppointmentTime,
+ printAppointments,
+ } = require("./day");
+
+ // The following is just a demo of how to use the functions.
+ // Remember to call setUpDay() before making any appointments.
+ // If you want to debug a test, you can change the code below to copy the test code.
+ console.log("Day Demo. Setting up an empty day.");
+ setUpDay();
+ printAppointments();
+ console.log("Making an appointment for John at 11am.");
+ makeAppointment(11, "John", 1);
+ printAppointments();
+ ```
+ At the top of the file we import the required functionality from `day.js` These are the functions you are allowed to call. Then we:
+
+ * call `setUpDay` to initialise an empty appointment array,
+ * print the appointments from the empty day
+ * make a one hour appointment for John at 11
+ * print the list of appointments again. This time we should see the new appointment at 11.
+
+1. Open a terminal window in the folder and enter:
+
+ ```console
+ npm run demo
+ ```
+ You should see the following output:
+ ```console
+ $ npm run demo
+
+ > jest@1.0.0 demo
+ > node dayDemo.js
+
+ Day Demo. Setting up an empty day.
+ Appointments for the day:
+ Time: 9, Name: available, Length: 0
+ Time: 10, Name: available, Length: 0
+ Time: 11, Name: available, Length: 0
+ Time: 12, Name: available, Length: 0
+ Time: 13, Name: available, Length: 0
+ Time: 14, Name: available, Length: 0
+ Time: 15, Name: available, Length: 0
+ Time: 16, Name: available, Length: 0
+ Time: 17, Name: available, Length: 0
+ Making an appointment for John at 11am.
+ Appointments for the day:
+ Time: 9, Name: available, Length: 0
+ Time: 10, Name: available, Length: 0
+ Time: 11, Name: John, Length: 1
+ Time: 12, Name: available, Length: 0
+ Time: 13, Name: available, Length: 0
+ Time: 14, Name: available, Length: 0
+ Time: 15, Name: available, Length: 0
+ Time: 16, Name: available, Length: 0
+ Time: 17, Name: available, Length: 0
+ ```
+
+ Check the output is what you expected given the code in `dayDemo.js`.
+
+## What does `makeAppointment` currently do?
+
+Imagine that you have been asked to implement the function called `makeAppointment`. The starting code for this function can be found near the bottom of `day.js` and it's current implementation is:
+
+```javascript
+// Make an appointment at a specific time.
+// THIS IS THE ONLY FUNCTION THAT YOU CAN CHANGE
+function makeAppointment(time, person, length) {
+ updateIndex(time, person, length);
+ return true;
+}
+```
+
+1. Don't change any code yet but open `day.js` and find the `makeAppointment` function. Also find the function called `updateIndex` which is the function that changes the contents of the array containing all of the appointments in the day.
+ > aside positive
+ >
+ > Note that we saw that for an empty appointment slot, the name was `available` and the length was `0`. To set up an empty day, we initialise every index in the array to the following value:
+ > ```javascript
+ > { name: "available", length: 0 }
+ > ```
+ > Once an appointment is made, the `name` property should contain the name of the person the appoinment is with. The `length` property should contain the length of the appointment.
+
+If you were to debug the code with a break point at the end of `makeAppointment` you will see the following:
+
+
+
+Appointments made for 9am are stored in index 0, appointments for 10am are stored in index 1, appointments for 11am are stored in index 2.
+
+Note that after we run the `dayDemo` and set an appointment for John at 11, **index 2** of the appointments array has been changed to:
+```javascript
+{ name: "John", length: 1 }
+```
+You can also see the values of the parameters `length`, `person` and `time` in the debugger.
+
+The code for `makeAppointment` is only the starting point for the function. Before we can change anything, we need to know the specification for that function.
+
+## The specification for `makeAppointment`
+
+Here is the **specification** (ie **the rules**) for the `makeAppointment` function. The specification tells us how the function should work.
+
+* The `makeAppointment` function will `return true` when the appointment was made successfully and `return false` when the appointment could not be made. There should be no exceptions generated.
+* The earliest time an appointment can be made is 9 (meaning 9:00).
+* The latest time an appointment can be made is 17 (meaning 17:00).
+* The length of an appountment will be provided in hours. A value of 1 means a one hour appointment, a value of 2 means a two hour appointment, and so on.
+* An appointment can only be successfully booked if **all** the time slots it will take up represent a valid time and contain `{ name: "available", ...}`. The value of `length` is not relevant when the value of `name` is `available`.
+ For example, if we wanted to make a 3 hour appointment for John, starting at 11, the result of printing the day should look like this:
+ ```console
+ Making a three hour appointment for John at 11am.
+ Appointments for the day:
+ Time: 9, Name: available, Length: 0
+ Time: 10, Name: available, Length: 0
+ Time: 11, Name: John, Length: 3
+ Time: 12, Name: John, Length: 3
+ Time: 13, Name: John, Length: 3
+ Time: 14, Name: available, Length: 0
+ Time: 15, Name: available, Length: 0
+ Time: 16, Name: available, Length: 0
+ Time: 17, Name: available, Length: 0
+ ```
+* No appointments may continue after 18:00, so you can only set a one hour appointment to start at 17:00.
+
+1. Take some time to look at these rules.
+1. Write down **five** different scenarios for making an appointment that should `return true` (ie they are allowed)
+1. Write down **five** different scenarios for making an appointment that should `return false` (ie they should not be allowed).
+
+## Test Driven Development
+
+The philosophy behind Test Driven Development (aka TDD) is that we should write a test first to check the functionality that we are about to write. We run the test and see that it fails. Then we implement the functionality and re-run the test and hopefully see that it passes.
+
+1. Open the file called `day.test.js` and have a look at the existing tests. There are three of them. Read the tests and try to understand what they do (**do not run the tests** yet).
+2. Do you understand what each of the three tests are testing for? If not ask a question.
+
+A good test should should have **three parts**:
+* **First:** Set everything up ready for the test
+* **Second:** Perform the action we are testing
+* **Third:** Check the results of the action to see that everything we `expect` to have happened has indeed happened.
+
+### Example: testing that `setUpDay` works correctly
+
+Here is the code to test `setUpDay`:
+```javascript
+// test that all the appointments on an empty day are available
+test("empty day", () => {
+ // nothing to set up
+ // perform the action we are testing
+ setUpDay();
+ // check the results are as we expected
+ const start = getFirstAppointmentTime();
+ const length = getLengthOfDay();
+ for (let time = start; time < length; time++) {
+ expect(getAppointment(time).name).toBe("available");
+ }
+});
+```
+
+Here there is nothing to set up. The **action** is that we call the function `setUpDay`. Checking requires we look at the array to see that `name` property has the value `available` for each hour of the day.
+
+### Example: testing we can make an appointment at 9:00
+
+Here is the test to make an appointment at the start of the day (at 9:00).
+```javascript
+// test that we can make an appointment at the start of an empty day
+test("Make Appointment at start of day", () => {
+ // set up everything ready for the test
+ setUpDay();
+ const time = getFirstAppointmentTime();
+ // perform the action
+ const result = makeAppointment(time, "John", 1);
+ // check the results are as expected
+ expect(result).toBe(true);
+ expect(getAppointment(time).name).toBe("John");
+ expect(getAppointment(time).length).toBe(1);
+});
+```
+Here there are two things to set up, first we need to call `setUpDay` to ensure the day's appointments are all available, and then we find the time of the first appointment of the day. Next we perform the action which is to make the appointment and get the returned `result`. Finally we check that the returned result was `true`, the name associated with the assigned appointment is `John` and the length associated with the assigned appointment is `1`.
+
+### Running the tests
+
+1. Run the tests by typing the following into the terminal window:
+ ```console
+ npm run test
+ ```
+1. Which tests pass and which test fails?
+1. Identify the failed test, where is it failing and what is going wrong. (**do not change any code at this time**)
+1. Explain what is causing the test to fail.
+
+### Discussion
+
+1. At this point we will have a discussion to check everyone is following and understands the tests.
+
+### Fixing the failed test
+
+1. Edit the code in `makeAppointment` to ensure that the method returns `false` as described in the specification. **Do not modify any existing function except for `makeAppointment`**.
+1. Rerun the tests and ensure that all tests pass.
+
+## Write some more tests.
+
+You should work in pairs to complete the following steps. If you finish this step and have time to spare, repeat the steps and write tests for other scenarios.
+
+1. Pick one of your five scenarios that should cause `makeAppointment` to return `true` and write a test to ensure that everything it needs to do has been done correctly.
+1. Run the test and see it fail
+1. Write the code to implement your scenario
+1. Rerun the tests and ensure it passes **before** you continue
+1. Pick one of your five scenarios that should cause `makeAppointment` to return `false` and write a test to ensure that nothing has changed in the appointment diary and that the returned value is `false`.
+1. Run the test and see it fail
+1. Write the code to implement your scenario
+1. Rerun the tests and ensure it passes **before** you continue
+
+> aside positive
+> Note that it is possible that the test passes without having to write any new code. This just means that the existing functionality includes the scenario you just wrote a test for. Pick another scenario and write a test for it.
+
+> aside positive
+> Remember that every good test should should have **three parts**:
+> * **First:** Set everything up ready for the test
+> * **Second:** Perform the action we are testing
+> * **Third:** Check the results of the action to see that everything we `expect` to have happened has indeed happened.
+
+
+## Summary
+
+* We engaged in TDD and wrote tests **before** writing the required functionality
+* We looked at some existing tests and how they worked
+* We looked at fixing the implementation to make a failed test pass.
+* We discovered that we may need to write a lot of tests to cover all possible scenarios.
diff --git a/testingWithJest/day.js b/testingWithJest/day.js
new file mode 100644
index 00000000..b0f13533
--- /dev/null
+++ b/testingWithJest/day.js
@@ -0,0 +1,72 @@
+// The appointments for the day.
+const appointments = [];
+// The hour of the first appointment of the day.
+const START_OF_DAY = 9;
+// The hour of the last appointment of the day.
+const FINAL_APPOINTMENT_TIME = 17;
+// The number of bookable hours in a day.
+const MAX_APPOINTMENTS_PER_DAY = FINAL_APPOINTMENT_TIME - START_OF_DAY + 1;
+
+// Set up the day with all available appointments.
+function setUpDay() {
+ for (let i = START_OF_DAY; i <= FINAL_APPOINTMENT_TIME; i++) {
+ // the 9am appointment goes in index 0, so we need to subtract the start time
+ appointments[i - START_OF_DAY] = { name: "available", length: 0 };
+ }
+}
+
+// insert an appointment at a specific time
+function updateIndex(time, person, length) {
+ const index = time - START_OF_DAY;
+ appointments[index].name = person;
+ appointments[index].length = length;
+}
+
+// Get the appointment at a specific time.
+function getAppointment(time) {
+ return appointments[time - START_OF_DAY];
+}
+
+// Get the time of the first appointment in the day.
+function getFirstAppointmentTime() {
+ return START_OF_DAY;
+}
+
+// Get the time of the last appointment in the day.
+function getLastAppointmentTime() {
+ return FINAL_APPOINTMENT_TIME;
+}
+
+// Get the number of appointment slots in the day.
+function getLengthOfDay() {
+ return MAX_APPOINTMENTS_PER_DAY;
+}
+
+// Print out the appointments for the day.
+function printAppointments() {
+ console.log("Appointments for the day:");
+ for (let i = START_OF_DAY; i <= FINAL_APPOINTMENT_TIME; i++) {
+ console.log(
+ `Time: ${i}, Name: ${appointments[i - START_OF_DAY].name}, Length: ${
+ appointments[i - START_OF_DAY].length
+ }`
+ );
+ }
+}
+
+// Make an appointment at a specific time.
+// THIS IS THE ONLY FUNCTION THAT YOU CAN CHANGE
+function makeAppointment(time, person, length) {
+ updateIndex(time, person, length);
+ return true;
+}
+
+module.exports = {
+ setUpDay,
+ makeAppointment,
+ getAppointment,
+ getLengthOfDay,
+ getFirstAppointmentTime,
+ getLastAppointmentTime,
+ printAppointments,
+};
diff --git a/testingWithJest/day.test.js b/testingWithJest/day.test.js
new file mode 100644
index 00000000..1f7c4f0b
--- /dev/null
+++ b/testingWithJest/day.test.js
@@ -0,0 +1,46 @@
+const {
+ setUpDay,
+ makeAppointment,
+ getAppointment,
+ getLengthOfDay,
+ getFirstAppointmentTime,
+ getLastAppointmentTime,
+} = require("./day");
+
+// test that all the appointments on an empty day are available
+test("empty day", () => {
+ // nothing to set up
+ // perform the action we are testing
+ setUpDay();
+ // check the results are as expected
+ const start = getFirstAppointmentTime();
+ const length = getLengthOfDay();
+ for (let time = start; time < length; time++) {
+ expect(getAppointment(time).name).toBe("available");
+ }
+});
+
+// test that we can make an appointment at the start of an empty day
+test("Make Appointment at start of day", () => {
+ // set up everything ready for the test
+ setUpDay();
+ const time = getFirstAppointmentTime();
+ // perform the action
+ const result = makeAppointment(time, "John", 1);
+ // check the results are as expected
+ expect(result).toBe(true);
+ expect(getAppointment(time).name).toBe("John");
+ expect(getAppointment(time).length).toBe(1);
+});
+
+// test that we can make an appointment at the start of an empty day
+test("Make Appointment before the start of day", () => {
+ // set up everything ready for the test
+ setUpDay();
+ const time = getFirstAppointmentTime() - 1;
+ // perform the action
+ const result = makeAppointment(time, "John", 1);
+ // check the results are as expected
+ expect(result).toBe(false);
+ expect(getAppointment(getFirstAppointmentTime()).name).toBe("available");
+});
diff --git a/testingWithJest/dayDemo.js b/testingWithJest/dayDemo.js
new file mode 100644
index 00000000..0bc60ce5
--- /dev/null
+++ b/testingWithJest/dayDemo.js
@@ -0,0 +1,19 @@
+const {
+ setUpDay,
+ makeAppointment,
+ getAppointment,
+ getLengthOfDay,
+ getFirstAppointmentTime,
+ getLastAppointmentTime,
+ printAppointments,
+} = require("./day");
+
+// The following is just a demo of how to use the functions.
+// Remember to call setUpDay() before making any appointments.
+// If you want to debug a test, you can change the code below to copy the test code.
+console.log("Day Demo. Setting up an empty day.");
+setUpDay();
+printAppointments();
+console.log("Making an appointment for John at 11am.");
+makeAppointment(11, "John", 1);
+printAppointments();
diff --git a/testingWithJest/docs/codelab.json b/testingWithJest/docs/codelab.json
new file mode 100644
index 00000000..877bddba
--- /dev/null
+++ b/testingWithJest/docs/codelab.json
@@ -0,0 +1,24 @@
+{
+ "environment": "web",
+ "format": "html",
+ "prefix": "https://storage.googleapis.com",
+ "mainga": "UA-49880327-14",
+ "updated": "2024-11-07T17:14:23Z",
+ "id": "docs",
+ "duration": 0,
+ "title": "Testing with Jest",
+ "summary": "Workshop on Jest for testing",
+ "source": "README.md",
+ "theme": "",
+ "status": [
+ "published"
+ ],
+ "category": [
+ "digital"
+ ],
+ "tags": [
+ "web"
+ ],
+ "feedback": "mailto:a.j.beaumont@aston.ac.uk",
+ "url": "docs"
+}
diff --git a/testingWithJest/docs/cyf.css b/testingWithJest/docs/cyf.css
new file mode 100644
index 00000000..47c9053c
--- /dev/null
+++ b/testingWithJest/docs/cyf.css
@@ -0,0 +1,24 @@
+ol[type="1"]::before {
+ font-weight: bold;
+ font-size: 1.875em;
+ color: #9A1750;
+ content: "Activity:";
+}
+ol[type="1"] {
+ padding-right: 1em;
+ border: thick double #E3AFBC;
+}
+
+ol[type="1"] ol[type="1"]::before {
+ content: "";
+}
+
+ol[type="1"] ol[type="1"] {
+ border: none;
+}
+
+
+ul.checklist li::marker {
+ content: '\2714\0020'; /* '✓'; */
+ color: green;
+}
diff --git a/testingWithJest/docs/img/2ac9cc8ff0ea544d.png b/testingWithJest/docs/img/2ac9cc8ff0ea544d.png
new file mode 100644
index 00000000..aa165bbc
Binary files /dev/null and b/testingWithJest/docs/img/2ac9cc8ff0ea544d.png differ
diff --git a/testingWithJest/docs/img/67453563068dff57.png b/testingWithJest/docs/img/67453563068dff57.png
new file mode 100644
index 00000000..8de2c825
Binary files /dev/null and b/testingWithJest/docs/img/67453563068dff57.png differ
diff --git a/testingWithJest/docs/img/d967ab98a3e98a2.png b/testingWithJest/docs/img/d967ab98a3e98a2.png
new file mode 100644
index 00000000..d94bc294
Binary files /dev/null and b/testingWithJest/docs/img/d967ab98a3e98a2.png differ
diff --git a/testingWithJest/docs/index.html b/testingWithJest/docs/index.html
new file mode 100644
index 00000000..ea926eed
--- /dev/null
+++ b/testingWithJest/docs/index.html
@@ -0,0 +1,334 @@
+
+
+
+
+
+
+
+
+ Testing with Jest
+
+
+
+
+
+
+
+
+
+
+
This workshop looks at writing unit tests in Jest.
You should fork and then clone the workshop repository which you will find here: https://github.com/beaumoaj/jestWorkshop. Note this repository is currently private, I will make it public at the start of the workshop for you to fork it.
+
+
+
+
+
+
+
Once you have forked the repository and cloned a copy to your computer, open the folder in VS Code. It should look like this:
+
+
This project contains the following files:
+
+
day.js which provides the functionality to store appointments during a given day.
+
dayDemo.js contains brief demo of how to use the existing code in day.js.
+
day.test.js contains the beginnings of a set of unit tests for day.js.
+
+
Running the code
+
+
Open the package.json first and look at the dependencies (you will see jest) and look at the scripts - you will see demo and test. The scripts definitions allow you to run two actions, demo and test (don't run them yet).
+
Open the file called dayTest.js. It constains the following code:
const {
+ setUpDay,
+ makeAppointment,
+ getAppointment,
+ getLengthOfDay,
+ getFirstAppointmentTime,
+ getLastAppointmentTime,
+ printAppointments,
+} = require("./day");
+
+// The following is just a demo of how to use the functions.
+// Remember to call setUpDay() before making any appointments.
+// If you want to debug a test, you can change the code below to copy the test code.
+console.log("Day Demo. Setting up an empty day.");
+setUpDay();
+printAppointments();
+console.log("Making an appointment for John at 11am.");
+makeAppointment(11, "John", 1);
+printAppointments();
+
+At the top of the file we import the required functionality from day.js These are the functions you are allowed to call. Then we:
+
call setUpDay to initialise an empty appointment array,
+
print the appointments from the empty day
+
make a one hour appointment for John at 11
+
print the list of appointments again. This time we should see the new appointment at 11.
+Check the output is what you expected given the code in dayDemo.js.
+
+
+
+
+
+
+
Imagine that you have been asked to implement the function called makeAppointment. The starting code for this function can be found near the bottom of day.js and it's current implementation is:
+
// Make an appointment at a specific time.
+// THIS IS THE ONLY FUNCTION THAT YOU CAN CHANGE
+function makeAppointment(time, person, length) {
+ updateIndex(time, person, length);
+ return true;
+}
+
+
+
Don't change any code yet but open day.js and find the makeAppointment function. Also find the function called updateIndex which is the function that changes the contents of the array containing all of the appointments in the day.
+
+
+
If you were to debug the code with a break point at the end of makeAppointment you will see the following:
+
+
Appointments made for 9am are stored in index 0, appointments for 10am are stored in index 1, appointments for 11am are stored in index 2.
+
Note that after we run the dayDemo and set an appointment for John at 11, index 2 of the appointments array has been changed to:
+
{ name: "John", length: 1 }
+
+
You can also see the values of the parameters length, person and time in the debugger.
+
The code for makeAppointment is only the starting point for the function. Before we can change anything, we need to know the specification for that function.
+
+
+
+
+
+
Here is the specification (ie the rules) for the makeAppointment function. The specification tells us how the function should work.
+
+
The makeAppointment function will return true when the appointment was made successfully and return false when the appointment could not be made. There should be no exceptions generated.
+
The earliest time an appointment can be made is 9 (meaning 9:00).
+
The latest time an appointment can be made is 17 (meaning 17:00).
+
The length of an appountment will be provided in hours. A value of 1 means a one hour appointment, a value of 2 means a two hour appointment, and so on.
+
An appointment can only be successfully booked if all the time slots it will take up represent a valid time and contain { name: "available", ...}. The value of length is not relevant when the value of name is available. For example, if we wanted to make a 3 hour appointment for John, starting at 11, the result of printing the day should look like this:
Making a three hour appointment for John at 11am.
+Appointments for the day:
+Time: 9, Name: available, Length: 0
+Time: 10, Name: available, Length: 0
+Time: 11, Name: John, Length: 3
+Time: 12, Name: John, Length: 3
+Time: 13, Name: John, Length: 3
+Time: 14, Name: available, Length: 0
+Time: 15, Name: available, Length: 0
+Time: 16, Name: available, Length: 0
+Time: 17, Name: available, Length: 0
+
+
+
+
No appointments may continue after 18:00, so you can only set a one hour appointment to start at 17:00.
+
+
+
Take some time to look at these rules.
+
Write down five different scenarios for making an appointment that should return true (ie they are allowed)
+
Write down five different scenarios for making an appointment that should return false (ie they should not be allowed).
+
+
+
+
+
+
+
The philosophy behind Test Driven Development (aka TDD) is that we should write a test first to check the functionality that we are about to write. We run the test and see that it fails. Then we implement the functionality and re-run the test and hopefully see that it passes.
+
+
Open the file called day.test.js and have a look at the existing tests. There are three of them. Read the tests and try to understand what they do (do not run the tests yet).
+
Do you understand what each of the three tests are testing for? If not ask a question.
+
+
A good test should should have three parts:
+
+
First: Set everything up ready for the test
+
Second: Perform the action we are testing
+
Third: Check the results of the action to see that everything we expect to have happened has indeed happened.
+
+
Example: testing that setUpDay works correctly
+
Here is the code to test setUpDay:
+
// test that all the appointments on an empty day are available
+test("empty day", () => {
+ // nothing to set up
+ // perform the action we are testing
+ setUpDay();
+ // check the results are as we expected
+ const start = getFirstAppointmentTime();
+ const length = getLengthOfDay();
+ for (let time = start; time < length; time++) {
+ expect(getAppointment(time).name).toBe("available");
+ }
+});
+
+
Here there is nothing to set up. The action is that we call the function setUpDay. Checking requires we look at the array to see that name property has the value available for each hour of the day.
+
Example: testing we can make an appointment at 9:00
+
Here is the test to make an appointment at the start of the day (at 9:00).
+
// test that we can make an appointment at the start of an empty day
+test("Make Appointment at start of day", () => {
+ // set up everything ready for the test
+ setUpDay();
+ const time = getFirstAppointmentTime();
+ // perform the action
+ const result = makeAppointment(time, "John", 1);
+ // check the results are as expected
+ expect(result).toBe(true);
+ expect(getAppointment(time).name).toBe("John");
+ expect(getAppointment(time).length).toBe(1);
+});
+
+
Here there are two things to set up, first we need to call setUpDay to ensure the day's appointments are all available, and then we find the time of the first appointment of the day. Next we perform the action which is to make the appointment and get the returned result. Finally we check that the returned result was true, the name associated with the assigned appointment is John and the length associated with the assigned appointment is 1.
+
Running the tests
+
+
Run the tests by typing the following into the terminal window:
npm run test
+
+
+
Which tests pass and which test fails?
+
Identify the failed test, where is it failing and what is going wrong. (do not change any code at this time)
+
Explain what is causing the test to fail.
+
+
Discussion
+
+
At this point we will have a discussion to check everyone is following and understands the tests.
+
+
Fixing the failed test
+
+
Edit the code in makeAppointment to ensure that the method returns false as described in the specification. Do not modify any existing function except for makeAppointment.
+
Rerun the tests and ensure that all tests pass.
+
+
+
+
+
+
+
You should work in pairs to complete the following steps. If you finish this step and have time to spare, repeat the steps and write tests for other scenarios.
+
+
Pick one of your five scenarios that should cause makeAppointment to return true and write a test to ensure that everything it needs to do has been done correctly.
+
Run the test and see it fail
+
Write the code to implement your scenario
+
Rerun the tests and ensure it passes before you continue
+
Pick one of your five scenarios that should cause makeAppointment to return false and write a test to ensure that nothing has changed in the appointment diary and that the returned value is false.
+
Run the test and see it fail
+
Write the code to implement your scenario
+
Rerun the tests and ensure it passes before you continue
+
+
+
+
+
+
+
+
+
+
We engaged in TDD and wrote tests before writing the required functionality
+
We looked at some existing tests and how they worked
+
We looked at fixing the implementation to make a failed test pass.
+
We discovered that we may need to write a lot of tests to cover all possible scenarios.
