---
# System prepended metadata

title: Testing your code schedule

---

# Testing your code schedule

Notebooks:
- 0: Intro: 5
- 1: How to test: 15 ([name=Ed] I think longer)
- 2: Testing frameworks: 15
- 3: Exercise (energy calculation): 30
- 4: Mocking: 15
- 5: Debugger: 10
- 6: CI: 5
- 7: Testing monte carlo code: ?

4 x 45 minute taught sessions (including hands-on exercises):
- 13:00-13:45
    - NB 0 Ed, 1 Andy
- (15 minute break)
- 14:00-14:45
    - NB 2 Ed, 3 Andy  (Notebook 3 is the energy example, give them 30 mins)
- (30 minute break)
- 15:15-16:00
    - NB 4 Ed, (5) Ed, 6 Andy
- (15 minute break)
- 16:15-17:00
    - NB 7 Andy


# Ed teaching notes:

### Intro

### Testing frameworks

### Mocking

- Patching allows you to choose which sub function of your function (e.g. the requests.get call that takes a url) to not call, but to mock

### Debugger

- Just briefly run through the commands in terminal