add testing

robvk · robvk · commit 5396c6cca953 · 2021-06-15T16:31:13.000+02:00
diff --git a/Week1/MAKEME.md b/Week1/MAKEME.md
@@ -21,9 +21,10 @@ The above should give you a nice basis. If you have extra time and are still a l
 - There is a practice-exercises folder in this week's repository that is filled with exercises to try out. The solutions are in a separate folder so you can check if you did it correctly. Clone this repository to your computer and have a go!
 
 ## No homework to hand in
+
 For the first 2 weeks of JavaScript there is no homework to hand in as the exercises already give you all the feedback you need. Go through the first 3 weeks at your own pace, and feel free to ask questions about any of the 3 weeks for the Q&A sessions.
 
 ## Done early?
 
-Have a look at some of the week2 concepts already and try to do more exercises in the links above. The first weeks of the JavaScript modules are very important as understanding the basics will make the rest of the curriculum that much easier to follow. So keep reading and writing code!
+Try to do more exercises in the links above. The first weeks of the JavaScript modules are very important as understanding the basics will make the rest of the curriculum that much easier to follow. So keep reading and writing code! If you are done early, go on to week 2!
 
diff --git a/Week2/MAKEME.md b/Week2/MAKEME.md
@@ -18,4 +18,4 @@ While there’s no homework to be handed in this week, we strongly suggest that
 
 ## Done early?
 
-Have a look at some of the week3 concepts already and try to do more exercises in the links above. The first weeks of the JavaScript modules are very important as understanding the basics will make the rest of the curriculum that much easier to follow. So keep reading and writing code!
+Try to do more exercises in the links above. The first weeks of the JavaScript modules are very important as understanding the basics will make the rest of the curriculum that much easier to follow. So keep reading and writing code! If you feel up to it, continue on to week 3 as then we bring everything together.
diff --git a/Week3/README.md b/Week3/README.md
@@ -8,6 +8,8 @@ These are the topics for week 3:
 2. [Scope](https://study.hackyourfuture.net/#/javascript/scope)
 3. [Modern JS](https://study.hackyourfuture.net/#/javascript/modern-js)
 4. [Continue with Your personal brand](https://github.com/HackYourFuture/yourpersonalbrand)
+5. [Testing code](https://www.ministryoftesting.com/dojo/series/the-testing-planet-2017/lessons/so-what-is-software-testing)
+   - [Assertion](https://study.hackyourfuture.net/#/testing/assertion)
 
 ## Week goals
 This week is the last week of explaining all the basic building blocks that JavaScript offers for you to work with. The last one is called functions, read all about them [here](https://study.hackyourfuture.net/#/javascript/functions). Functions bring along with them a concept called the scope that you may have encountered a bit last week but we want to explicitely explain now. Read about scope [here](https://study.hackyourfuture.net/#/javascript/scope).
@@ -16,6 +18,8 @@ These things will take the power of what you can do to another level, as it allo
 
 Now that you have learned all the basic blocks it is time to tell you about the different versions of JavaScript. JavaScript has been evolving over its lifetime and certain syntax has been added. Have a look in your study book at the topic of what is called 'Modern JS' [here](https://study.hackyourfuture.net/#/javascript/modern-js). Throughout the curriculum we will be expecting you to use the modern syntax as that is most likely what you will be programming in. You can skip the sections that are about Promises and async/await for now, we will get there in the Using API's module. There is also a section on the history of JavaScript in there, you do not need to know this but we recommend it if you have some time to spare as it is very interesting.
 
+Lastly we want to introduce the first steps to testing code. Let's first have a look at what software testing is and why we do it [here](https://www.ministryoftesting.com/dojo/series/the-testing-planet-2017/lessons/so-what-is-software-testing). The simplest form of testing is using assertions, have a look what that is [here](https://study.hackyourfuture.net/#/testing/assertion), we will introduce this more in your homework.
+
 Also, don't forget about the [personal brand repo](https://github.com/HackYourFuture/yourpersonalbrand) if you didn't manage to complete it last week.
 
 ## Finished?
diff --git a/Week4/README.md b/Week4/README.md
@@ -10,14 +10,18 @@ These are the topics for week 4:
    - Execution context
    - Why do we need closures?
 3. [Problem solving](https://study.hackyourfuture.net/#/programming/problem-solving-process)
-4. [Continue with Your personal brand](https://github.com/HackYourFuture/yourpersonalbrand)
+4. [Unit testing](https://study.hackyourfuture.net/#/testing/unit-tests)
+   - [Testing framework (Jest)](https://study.hackyourfuture.net/#/tools/test-framework)
+5. [Finalise Your personal brand](https://github.com/HackYourFuture/yourpersonalbrand)
 
 ## Week goals
 
 This week we are going to keep practicing coding and introducing a few more advanced topics that you will encounter. So a little less reading, more practicing! Firstly, higher order functions are a way functions are being used regularly in the real world, most notably in the methods `Array`'s provide us. Read all about it [here](https://study.hackyourfuture.net/#/javascript/higher-order-functions). Secondly, JavaScript has a thing called closures which you should know about. You will not encounter issues with them any time soon, but it is good to have in the back of your mind that this exists. So read all about them [here](https://study.hackyourfuture.net/#/javascript/closures).
 
 Now that we are getting into more and more complex code it is also a good idea to learn a structured way to solve more complex problems. Have a look at the page on problem solving in your study book over [here](https://study.hackyourfuture.net/#/programming/problem-solving-process).
 
+Last week we learned about the `assert` function which allow us to make code checks, but that is only the start. For real testing we developers write something we call unit tests, have a look at what that means [here](https://study.hackyourfuture.net/#/testing/unit-tests). Then have a look at test frameworks and what they can do over [here](https://study.hackyourfuture.net/#/tools/test-framework). Note that in our curriculum we will always be using *Jest* as it is very popular and works well with React which we will be studying later. Behind the scenes we have been testing your homework with Jest all this time and it is where the error messages when running your homework comes from!
+
 After that it is time to start practicing again, make as many exercises as you can in the list [here](./MAKEME.md) and don't forget to hand in your homework. There will also be a test coming up for this module. What and when will be announced in your class channel, so keep an eye on that as usual! The best way to prepare is to keep programming!
 
 Also, don't forget about the [personal brand repo](https://github.com/HackYourFuture/yourpersonalbrand) if you didn't manage to complete it last week.

Original file line number	Diff line number	Diff line change
`@@ -18,4 +18,4 @@ While there’s no homework to be handed in this week, we strongly suggest that`
`18`	`18`
`19`	`19`	`## Done early?`
`20`	`20`
`21`		`-Have a look at some of the week3 concepts already and try to do more exercises in the links above. The first weeks of the JavaScript modules are very important as understanding the basics will make the rest of the curriculum that much easier to follow. So keep reading and writing code!`
	`21`	`+Try to do more exercises in the links above. The first weeks of the JavaScript modules are very important as understanding the basics will make the rest of the curriculum that much easier to follow. So keep reading and writing code! If you feel up to it, continue on to week 3 as then we bring everything together.`