diff --git a/coderefinery-2025-september/editlist.yaml b/coderefinery-2025-september/editlist.yaml index a32c50d..0e35767 100644 --- a/coderefinery-2025-september/editlist.yaml +++ b/coderefinery-2025-september/editlist.yaml @@ -607,3 +607,104 @@ # - 04:54:25: Outro, where to go from here. # #- 05:07:11: General Q&A, more about AI code # - stop: 05:14:32 + +# Day 7 +- input: raw/day7-obs.mkv +- schedule-sync: 00:04:13=11:00:00 + +- output: out/day7-intro.mkv + title: 7.1 Day 7 intro + description: > + The introduction to day 7, where we present the event page on the CodeRefinery website + and the collaborative notes. + time: + - start: 00:14:01 + - -: Introduction and walkthrough + - end: 00:17:09 + +- output: out/day7-jupyter.mkv + title: 7.2 Jupyter + description: > + This lesson teachs learners the user interface of JupyterLab, how + Jupyter notebooks work, and what some common and powerful usecases + are. Our focus is to demonstrate and discuss and guide towards + good practices for reproducibility, collaboration, and + reusability. The emphasis of this lesson is to demonstrate how to + use notebooks in combination with version control and how to share + reproducible notebooks via Binder. + + This lesson demonstrates the use of JupyterLab, nbdime, + jupyterlab-git, and Binder. + + https://coderefinery.github.io/jupyter/ + time: + - start: 00:17:25 + - -: Introduction + - 00:17:59: § Motivation for Jupyter Notebooks + - 00:34:52: § JupyterLab and notebook interface + - 00:51:57: § A first computational notecbook + - exercise: 00:55:48 + - start: 01:14:11 + - -: Exercise on "Calculating pi using Monte Carlo methods" as a demo + - break: 01:21:38 + - start: 01:31:39 + - -: Short note on other alternatives to Jupyter Notebooks and keypoints + - 01:33:35: § Notebooks and version control + - 01:44:02: § Sharing Notebooks + - exercise: 01:52:17 + - start: 02:08:34 + - 02:09:04: Exercise on Binder as a demo + - 02:16:46: § Examples of Jupyter features: Widgets + - 02:27:09: Summary and answer to use of rich-diff on GitHub + - 02:33:41: Feedback of the day and preparation for day 8 + - stop: 02:38:54 + +# Day 8 +- input: raw/day8-obs.mkv +- schedule-sync: 00:03:35=11:00:00 + +- output: out/day8-intro.mkv + title: 8.1 Day 8 intro + description: > + The introduction to day 8, where we present the event page on the coderefinery website + and the collaborative notes. + time: + - start: 00:03:35 + - -: Introduction and walkthrough + - end: 00:14:27 + +- output: out/day8-testing.mkv + title: 8.2 Automated Testing + description: > + Software testing is a fundamental part of modern software + development, and especially important for science since results + should be correct. Luckily, it's not so hard to get started, and + anyone can do it. This is a crash course for scientists to get + started testing their software. + + Tools covered include concepts of testing for science, unit + testing, pytest, continuous integration, and GitHub actions. We + make demos in Python, but have examples in other languages and + this will apply to every language in some form. + + https://coderefinery.github.io/testing/ + + time: + - start: 00:14:52 + - -: Introduction + - 00:18:58: § Motivation + - 00:40:24: § Testing localy (Pytest) + - exercise: 00:43:33 + - start: 01:03:44 + - -: Exercise discussion (testing locally) + - 01:08:12: §Continuous integration demo using Github actions + - break: 01:36:59 + - start: 01:47:19 + - -: § Test design + - exercise: 01:51:03 + - start: 02:11:35 + - -: Exercise discussion + - 02:12:07: §Testing locally - Other frameworks (C++/Catch2) + - 02:21:24: § Conclusions + - 02:32:58: Feedback and outlook for next lesson + - stop: 02:37:21 diff --git a/coderefinery-2025-september/raw/day8-obs.srt b/coderefinery-2025-september/raw/day8-obs.srt index a6b22bc..591352e 100644 --- a/coderefinery-2025-september/raw/day8-obs.srt +++ b/coderefinery-2025-september/raw/day8-obs.srt @@ -20,7 +20,7 @@ we are still here. 6 00:03:49,044 --> 00:03:52,389 -And let's do maybe a quick sound check. +And let's do a quick sound check. 7 00:03:52,389 --> 00:03:54,332 @@ -56,7 +56,7 @@ Yeah. 15 00:04:09,509 --> 00:04:11,151 -So I guess we'll count +So we'll count 16 00:04:11,151 --> 00:04:11,832 @@ -216,7 +216,7 @@ Okay. 55 00:05:29,586 --> 00:05:30,447 -Now it's visible maybe. +Now it's visible. 56 00:05:32,502 --> 00:05:35,047 @@ -308,11 +308,11 @@ Well, it's mostly Python, I'd say, 78 00:06:19,204 --> 00:06:21,206 -and maybe then it's occasionally +and then it's occasionally 79 00:06:21,206 --> 00:06:24,329 -some bash for smaller scripting, +some Bash for smaller scripting, 80 00:06:25,190 --> 00:06:25,891 @@ -336,7 +336,7 @@ So I'm working a lot with 85 00:06:32,097 --> 00:06:35,120 -bash in Python in daily work. +Bash in Python in daily work. 86 00:06:36,361 --> 00:06:37,863 @@ -440,7 +440,7 @@ So in your daily life, do you test, [name]? 111 00:07:28,096 --> 00:07:32,440 -So well, not in my sort of +So well, not in my 112 00:07:32,440 --> 00:07:33,822 @@ -464,7 +464,7 @@ Yes. 117 00:07:41,929 --> 00:07:43,111 -Yeah, I guess we'll talk +Yeah, we'll talk 118 00:07:43,111 --> 00:07:44,212 @@ -476,7 +476,7 @@ about the different types of 120 00:07:45,633 --> 00:07:46,974 -testing that are maybe relevant. +testing that are relevant. 121 00:07:46,974 --> 00:07:47,795 @@ -520,7 +520,7 @@ where I'm working. 131 00:08:13,900 --> 00:08:16,822 -Then, yeah, maybe by default, +Then, yeah, by default, 132 00:08:16,822 --> 00:08:17,843 @@ -592,7 +592,7 @@ in the machine learning context, 149 00:09:04,795 --> 00:09:06,917 -you know, GPU stuff. +GPU stuff. 150 00:09:07,978 --> 00:09:09,199 @@ -608,7 +608,7 @@ in a similar support role, but 153 00:09:13,463 --> 00:09:14,904 -kind of a little bit more like +a little bit more like 154 00:09:14,904 --> 00:09:17,246 @@ -648,7 +648,7 @@ And that's a machine named 163 00:09:38,530 --> 00:09:43,940 -.del, which has AMD CPUs and GPUs. +Dardel, which has AMD CPUs and GPUs. 164 00:09:43,940 --> 00:09:46,323 @@ -660,7 +660,7 @@ as the similar configuration as 166 00:09:48,806 --> 00:09:52,630 -you have on the Lumi supercomputer in Finland. +you have on the LUMI supercomputer in Finland. 167 00:09:52,630 --> 00:09:56,034 @@ -680,7 +680,7 @@ So a lot of the work that 171 00:10:01,821 --> 00:10:04,104 -I do at BDC is connecting +I do at PDC is connecting 172 00:10:04,104 --> 00:10:07,953 @@ -720,7 +720,7 @@ Welcome everyone to day 181 00:10:32,067 --> 00:10:35,292 -eight of the Code Refinery workshop, +eight of the CodeRefinery workshop, 182 00:10:35,292 --> 00:10:37,034 @@ -764,7 +764,7 @@ My name is [name]. 192 00:10:57,886 --> 00:11:00,249 -I'm project manager for Code Refinery +I'm project manager for CodeRefinery 193 00:11:00,249 --> 00:11:03,512 @@ -780,7 +780,7 @@ So what I wanted to show 196 00:11:07,176 --> 00:11:11,841 -you is first our workshop event page. +you is, first, our workshop event page. 197 00:11:11,841 --> 00:11:14,564 @@ -788,7 +788,7 @@ you is first our workshop event page. 198 00:11:15,425 --> 00:11:16,586 -Yes, so hopefully you know +Yes, so hopefully 199 00:11:16,586 --> 00:11:18,629 @@ -1164,7 +1164,7 @@ With me here for this lesson, 292 00:15:04,953 --> 00:15:08,601 -I have [name] from CSE. +I have [name] from CSC. 293 00:15:09,603 --> 00:15:10,264 @@ -1220,7 +1220,7 @@ Well, for me, I'd say there 306 00:15:48,742 --> 00:15:50,884 -are, I guess, several aspects to it. +are, several aspects to it. 307 00:15:52,686 --> 00:15:53,527 @@ -1256,7 +1256,7 @@ So I'm going to test that. 315 00:16:09,365 --> 00:16:13,170 -And I guess slightly related +And slightly related 316 00:16:13,170 --> 00:16:17,657 @@ -1420,11 +1420,11 @@ we encourage you to work 356 00:18:12,644 --> 00:18:15,468 -primarily with python and within +primarily with Python and within 357 00:18:15,468 --> 00:18:18,212 -the code refinery conda environment +the CodeRefinery conda environment 358 00:18:18,212 --> 00:18:22,919 @@ -1440,7 +1440,7 @@ for performing testing working 361 00:18:28,247 --> 00:18:33,275 -with python code bases there are similar +with Python code bases there are similar 362 00:18:33,275 --> 00:18:35,078 @@ -1476,11 +1476,11 @@ so one aspect of testing 370 00:19:04,444 --> 00:19:06,526 -is that maybe we're working +is that we're working 371 00:19:06,526 --> 00:19:10,090 -here with software and computing um +here with software and computing 372 00:19:10,090 --> 00:19:11,252 @@ -1652,11 +1652,11 @@ what you're using. 414 00:20:50,042 --> 00:20:53,127 -So they sort of all of +So they all of 415 00:20:53,127 --> 00:20:57,273 -the sort of assurances they could +the assurances they could 416 00:20:57,273 --> 00:20:59,557 @@ -1732,7 +1732,7 @@ it's not infinitely strongly 434 00:21:50,985 --> 00:21:56,290 -correlated with those sort of safety +correlated with those safety 435 00:21:56,290 --> 00:21:58,312 @@ -1876,7 +1876,7 @@ That could rather be... My experience of... 470 00:23:42,543 --> 00:23:49,490 -of things going wrong with, I mean, +of things going wrong with, 471 00:23:49,490 --> 00:23:51,112 @@ -1932,7 +1932,7 @@ We will come very soon here 484 00:24:24,983 --> 00:24:27,446 -to various kind of tests. +to various tests. 485 00:24:27,446 --> 00:24:30,531 @@ -1948,7 +1948,7 @@ we have complex numerical modeling where 488 00:24:39,344 --> 00:24:40,465 -I mean, naturally, you do +naturally, you do 489 00:24:40,465 --> 00:24:41,707 @@ -1988,7 +1988,7 @@ that these are correct or things 498 00:25:07,529 --> 00:25:09,793 -are, let's say you get it to a zero result +are, let's say, you get it to a zero result 499 00:25:09,793 --> 00:25:11,335 @@ -2028,11 +2028,11 @@ you cannot really arrive to 508 00:25:31,725 --> 00:25:36,372 -the, like the full 100% confidence +the full 100% confidence 509 00:25:36,372 --> 00:25:38,095 -is sort of an asymptotic. +... it is an asymptotic. 510 00:25:40,338 --> 00:25:41,299 @@ -2096,7 +2096,7 @@ And this now will illustrate 525 00:26:30,618 --> 00:26:33,602 -use of the PyTest framework. +use of the pytest framework. 526 00:26:33,602 --> 00:26:35,785 @@ -2132,7 +2132,7 @@ And now I just run it. 534 00:27:00,630 --> 00:27:01,111 -PyTest. +pytest. 535 00:27:03,795 --> 00:27:05,036 @@ -2144,7 +2144,7 @@ So what happened here is 537 00:27:07,540 --> 00:27:09,603 -that PyTest have looked here +that pytest have looked here 538 00:27:09,603 --> 00:27:12,788 @@ -2312,7 +2312,7 @@ start out from something that 579 00:29:20,401 --> 00:29:21,702 -you know is working and then +is working and then 580 00:29:21,702 --> 00:29:23,203 @@ -2392,11 +2392,11 @@ So testing an entire neural network, 599 00:30:14,701 --> 00:30:16,344 -That's kind of difficult because +That's difficult because 600 00:30:16,344 --> 00:30:18,287 -it's kind of stochastic and it's a black box. +it's stochastic and it's a black box. 601 00:30:18,287 --> 00:30:22,394 @@ -2408,7 +2408,7 @@ Then I focus more on things 603 00:30:23,837 --> 00:30:27,944 -that I can test well, like if +that I can test well, if 604 00:30:27,944 --> 00:30:29,186 @@ -2436,7 +2436,7 @@ For the example, things that 610 00:30:39,411 --> 00:30:41,538 -are sort of obviously correct, I +are obviously correct, I 611 00:30:41,538 --> 00:30:43,183 @@ -2448,7 +2448,7 @@ it can be good to write a test. 613 00:30:49,396 --> 00:30:50,437 -maybe it's not very high +it's not very high 614 00:30:50,437 --> 00:30:52,119 @@ -2484,7 +2484,7 @@ but also to make sure that 622 00:31:05,753 --> 00:31:07,015 -you were sort of thinking correctly. +you were thinking correctly. 623 00:31:12,140 --> 00:31:14,223 @@ -2508,7 +2508,7 @@ lot of overhead. 628 00:31:24,829 --> 00:31:26,232 -And let's say that the +And that the 629 00:31:26,232 --> 00:31:28,135 @@ -2540,7 +2540,7 @@ workflow that that you get up 636 00:31:45,900 --> 00:31:48,664 -and started with because with pi test +and started with because with pytest 637 00:31:48,664 --> 00:31:50,146 @@ -2548,11 +2548,11 @@ and we'll also see a 638 00:31:50,146 --> 00:31:53,651 -program here called catch2 for c++ +program here called Catch2 for c++ 639 00:31:53,651 --> 00:31:55,974 -code then i mean you do +code then you do 640 00:31:55,974 --> 00:31:59,419 @@ -2572,7 +2572,7 @@ run them in in a quasi-automated manner 644 00:32:10,160 --> 00:32:14,047 -So I really like PyTest in +So I really like pytest in 645 00:32:14,047 --> 00:32:15,911 @@ -2596,7 +2596,7 @@ and you did not even 650 00:32:21,722 --> 00:32:23,605 -import anything from PyTest or anything. +import anything from pytest or anything. 651 00:32:23,605 --> 00:32:25,168 @@ -2616,7 +2616,7 @@ And you made an assertion, 655 00:32:28,254 --> 00:32:30,157 -which is also not really part of PyTest. +which is also not really part of pytest. 656 00:32:30,157 --> 00:32:31,540 @@ -2628,7 +2628,7 @@ And yeah, that's why I 658 00:32:33,263 --> 00:32:35,528 -really like PyTest in that sense. +really like pytest in that sense. 659 00:32:35,528 --> 00:32:36,550 @@ -2656,7 +2656,7 @@ It's neat that it's readily 665 00:32:49,394 --> 00:32:51,578 -available and sort of not +available and not 666 00:32:51,578 --> 00:32:52,941 @@ -2684,7 +2684,7 @@ but go through the various 672 00:33:15,953 --> 00:33:19,617 -kind of tests and testing concepts +tests and testing concepts 673 00:33:19,617 --> 00:33:21,625 @@ -2708,7 +2708,7 @@ misunderstand what tests are 678 00:33:32,077 --> 00:33:33,559 -actually being run for a code. +being run for a code. 679 00:33:34,981 --> 00:33:38,265 @@ -2792,7 +2792,7 @@ program is working together. 699 00:34:27,700 --> 00:34:30,824 -So let's say you have like +So you have like 700 00:34:30,824 --> 00:34:34,769 @@ -2844,7 +2844,7 @@ here certainly it depends a bit 712 00:35:02,864 --> 00:35:06,287 -on what kind of program you're working with. +on what program you're working with. 713 00:35:07,128 --> 00:35:10,294 @@ -2852,7 +2852,7 @@ But it could be that that will involve, 714 00:35:10,294 --> 00:35:12,057 -so to say, the whole code base, +the whole code base, 715 00:35:13,219 --> 00:35:17,467 @@ -2872,7 +2872,7 @@ And I'd say that this is something which, 719 00:35:27,745 --> 00:35:28,827 -if you have, let's say, +if you have, 720 00:35:28,827 --> 00:35:32,120 @@ -2880,7 +2880,7 @@ in scientific computing, numerical modeling, 721 00:35:32,120 --> 00:35:34,182 -some use cases where you, let's say, +some use cases where you, 722 00:35:34,182 --> 00:35:36,465 @@ -2916,7 +2916,7 @@ hand, have something which is 730 00:35:50,082 --> 00:35:53,426 -more, let's say, event driven +more, event driven 731 00:35:54,307 --> 00:35:57,891 @@ -2928,7 +2928,7 @@ then it could be perhaps 733 00:36:01,512 --> 00:36:03,594 -much more challenging actually to +much more challenging to 734 00:36:03,594 --> 00:36:05,016 @@ -2988,7 +2988,7 @@ mean, written in a correct manner, 748 00:36:45,108 --> 00:36:47,813 -but also that you compare with, let's say, +but also that you compare with, 749 00:36:47,813 --> 00:36:49,055 @@ -3008,7 +3008,7 @@ That could be, so to 753 00:36:54,580 --> 00:36:56,925 -say, perhaps among your colleagues +say, among your colleagues 754 00:36:56,925 --> 00:37:00,212 @@ -3040,7 +3040,7 @@ And [name], what can that be about? 761 00:37:21,168 --> 00:37:24,775 -So, well, normally you maybe +So, well, normally you 762 00:37:24,775 --> 00:37:28,083 @@ -3056,7 +3056,7 @@ want to write. 765 00:37:31,510 --> 00:37:34,032 -and maybe don't think as much about +and don't think as much about 766 00:37:34,032 --> 00:37:36,454 @@ -3068,7 +3068,7 @@ that what you're writing is 768 00:37:38,456 --> 00:37:39,637 -actually being used and +being used and 769 00:37:39,637 --> 00:37:42,960 @@ -3076,7 +3076,7 @@ test-driven development is one way 770 00:37:42,960 --> 00:37:45,042 -where you can try and sort of invert +where you can try and invert 771 00:37:45,042 --> 00:37:46,383 @@ -3100,7 +3100,7 @@ about to write and yeah then 776 00:37:55,151 --> 00:37:57,232 -sort of continue developing that +continue developing that 777 00:37:57,232 --> 00:38:01,396 @@ -3136,7 +3136,7 @@ an interesting approach to have 785 00:38:17,021 --> 00:38:19,524 -a different sort of viewpoint on +a different viewpoint on 786 00:38:19,524 --> 00:38:21,568 @@ -3148,11 +3148,11 @@ Yeah. 788 00:38:25,595 --> 00:38:28,783 -that's um yeah indeed and +that's yeah indeed and 789 00:38:28,783 --> 00:38:33,636 -and um sometimes and and uh if +and sometimes and and if 790 00:38:33,636 --> 00:38:34,779 @@ -3164,7 +3164,7 @@ audience here perhaps you're working 792 00:38:36,183 --> 00:38:39,030 -at uh private companies and and um +at private companies and and 793 00:38:41,542 --> 00:38:43,964 @@ -3172,7 +3172,7 @@ What we can often see is, 794 00:38:43,964 --> 00:38:46,066 -I mean, comparing a little bit +comparing a little bit 795 00:38:46,066 --> 00:38:48,929 @@ -3184,7 +3184,7 @@ in corporate settings, you often have, 797 00:38:53,333 --> 00:38:54,574 -I mean, you have larger +you have larger 798 00:38:54,574 --> 00:38:56,696 @@ -3240,7 +3240,7 @@ by other members of the team. 811 00:39:29,310 --> 00:39:31,773 -So this is, I mean, it's clear here. +So this is, it's clear here. 812 00:39:31,773 --> 00:39:33,455 @@ -3252,7 +3252,7 @@ of these various things, all 814 00:39:36,718 --> 00:39:38,961 -kind of different tests, it helps +different tests, it helps 815 00:39:38,961 --> 00:39:40,843 @@ -3260,11 +3260,11 @@ if you are a large team. 816 00:39:42,292 --> 00:39:44,194 -But I guess usually in a scientific, well, +But usually in a scientific, well, 817 00:39:44,194 --> 00:39:45,435 -maybe it depends a little bit +it depends a little bit 818 00:39:45,435 --> 00:39:47,057 @@ -3356,7 +3356,7 @@ And testing locally is, I would say, 840 00:40:49,523 --> 00:40:51,806 -that's sort of the base case +that's the base case 841 00:40:51,806 --> 00:40:53,668 @@ -3368,7 +3368,7 @@ on your local computer. 843 00:40:55,891 --> 00:40:57,774 -Then in, so to say, real +Then in, real 844 00:40:57,774 --> 00:40:59,936 @@ -3392,7 +3392,7 @@ briefly introduce the exercise and 849 00:41:12,803 --> 00:41:15,806 -and perhaps um have some posted +and perhaps have some posted 850 00:41:15,806 --> 00:41:18,108 @@ -3408,7 +3408,7 @@ there are two tests here testing 853 00:41:27,118 --> 00:41:29,841 -um local one and local two +local one and local two 854 00:41:31,222 --> 00:41:33,852 @@ -3604,7 +3604,7 @@ collaborative document and we would 902 01:04:08,253 --> 01:04:12,441 -like to highlight some of of +to highlight some of of 903 01:04:12,441 --> 01:04:16,306 @@ -3668,11 +3668,11 @@ discussion here the question and 918 01:05:12,320 --> 01:05:19,209 -answer is that um for something +answer is that for something 919 01:05:19,209 --> 01:05:21,872 -like like a big deep learning model +like a big deep learning model 920 01:05:21,872 --> 01:05:23,134 @@ -3684,7 +3684,7 @@ to train you might want to do the testing 922 01:05:25,877 --> 01:05:28,000 -for so to say smaller cases +for smaller cases 923 01:05:28,000 --> 01:05:30,202 @@ -3724,7 +3724,7 @@ And so, or it's, yeah, you don't have like, 932 01:05:56,268 --> 01:05:58,531 -it's often not sort of +it's often not 933 01:05:58,531 --> 01:05:59,652 @@ -3808,7 +3808,7 @@ you need to check up on what, 953 01:06:52,555 --> 01:06:54,196 -or let's say, the keyword +or the keyword 954 01:06:54,196 --> 01:06:56,999 @@ -3816,7 +3816,7 @@ constructs in the respective framework. 955 01:06:56,999 --> 01:06:59,822 -So for PyTest, it's test underscore. +So for pytest, it's test underscore. 956 01:06:59,822 --> 01:07:07,148 @@ -3832,11 +3832,11 @@ or to regular start the 959 01:07:10,193 --> 01:07:14,499 -tests with with macros so uh +tests with with macros so 960 01:07:17,043 --> 01:07:20,929 -yeah you you simply um need to follow +yeah you you simply need to follow 961 01:07:20,929 --> 01:07:22,050 @@ -3848,7 +3848,7 @@ see a bit later here one example 963 01:07:23,793 --> 01:07:25,455 -of how that is done with uh +of how that is done with 964 01:07:25,455 --> 01:07:29,241 @@ -3972,7 +3972,7 @@ We will not notice it at first, 994 01:09:14,572 --> 01:09:16,734 -but when we start to run, let's say, +but when we start to run, 995 01:09:16,734 --> 01:09:17,735 @@ -4012,7 +4012,7 @@ collaborative code development, is 1004 01:09:39,837 --> 01:09:41,219 -that, I mean, you make a note +that, you make a note 1005 01:09:41,219 --> 01:09:43,043 @@ -4052,7 +4052,7 @@ and work out and okay how 1014 01:10:04,839 --> 01:10:08,303 -can i fix this and then go ahead and fix it +can I fix this and then go ahead and fix it 1015 01:10:08,303 --> 01:10:10,586 @@ -4064,7 +4064,7 @@ in a feature bronze and and and 1017 01:10:13,670 --> 01:10:15,612 -you push it to the github repo +you push it to the GitHub repo 1018 01:10:17,785 --> 01:10:20,108 @@ -4084,7 +4084,7 @@ tests will be run directly after pushing 1022 01:10:29,521 --> 01:10:30,782 -so that this, so to say, +so that this, 1023 01:10:30,782 --> 01:10:32,505 @@ -4096,7 +4096,7 @@ tested to see whether it 1025 01:10:36,130 --> 01:10:39,183 -actually then have resolved the bug. +then have resolved the bug. 1026 01:10:39,183 --> 01:10:41,986 @@ -4340,7 +4340,7 @@ of this one, we can test the code locally. 1086 01:15:00,906 --> 01:15:02,149 -So PyTest. +So pytest. 1087 01:15:04,070 --> 01:15:05,032 @@ -4444,7 +4444,7 @@ what is coming up here as 1112 01:16:37,955 --> 01:16:43,001 -a template is this within the .github +a template is this within the.GitHub 1113 01:16:43,001 --> 01:16:45,103 @@ -4556,7 +4556,7 @@ to measure coverage and this is a 1140 01:18:28,634 --> 01:18:30,136 -way to do it sort of automatically. +way to do it automatically. 1141 01:18:30,136 --> 01:18:32,159 @@ -4604,7 +4604,7 @@ because I think the the 1152 01:19:01,319 --> 01:19:05,386 -coverage testing here is um +coverage testing here is 1153 01:19:06,928 --> 01:19:08,951 @@ -4620,7 +4620,7 @@ being touched while executing the 1156 01:19:14,500 --> 01:19:19,628 -tests so it's sort of a metric with this +tests so it's a metric with this 1157 01:19:21,987 --> 01:19:23,849 @@ -4644,7 +4644,7 @@ but doesn't say anything about 1162 01:19:32,759 --> 01:19:36,162 -how, let's say central or this +how, central or this 1163 01:19:36,162 --> 01:19:37,564 @@ -4712,7 +4712,7 @@ that in the last commit message 1179 01:20:34,697 --> 01:20:38,121 -is that we created this python-app.yml file. +is that we created this Python-app.yml file. 1180 01:20:39,122 --> 01:20:43,026 @@ -4800,7 +4800,7 @@ So I go to my terminal and I type git pull. 1201 01:22:08,219 --> 01:22:13,186 -So now, yeah, this python-app.yaml +So now, yeah, this Python-app.yaml 1202 01:22:13,186 --> 01:22:15,269 @@ -4824,7 +4824,7 @@ this test underscore functions file. 1207 01:22:30,577 --> 01:22:39,029 -So we already had, so here, uh, yeah, +So we already had, so here, yeah, 1208 01:22:39,029 --> 01:22:41,793 @@ -4840,7 +4840,7 @@ have more clear colors on the, on the screen. 1211 01:22:47,721 --> 01:22:47,781 -Uh, + 1212 01:22:51,102 --> 01:22:52,885 @@ -5080,7 +5080,7 @@ So I just, I forked the repository. 1271 01:26:18,626 --> 01:26:21,230 -I guess I should sync it. +I should sync it. 1272 01:26:21,230 --> 01:26:22,052 @@ -5152,7 +5152,7 @@ Then look at the code that 1289 01:27:24,893 --> 01:27:25,974 -is being run, maybe. +is being run,. 1290 01:27:27,296 --> 01:27:27,817 @@ -5224,7 +5224,7 @@ Yeah. 1307 01:28:14,047 --> 01:28:17,733 -But I am... Yeah, I guess +But I am... Yeah, 1308 01:28:17,733 --> 01:28:19,917 @@ -5284,7 +5284,7 @@ to commit my changes. 1322 01:28:43,669 --> 01:28:48,515 -So, yeah, fixed subtraction, I guess. +So, yeah, fixed subtraction,. 1323 01:28:50,597 --> 01:28:52,560 @@ -5300,7 +5300,7 @@ should I put that in the pull request message? 1326 01:28:58,927 --> 01:29:00,509 -So, I mean, here you tested +So, here you tested 1327 01:29:00,509 --> 01:29:02,732 @@ -5312,7 +5312,7 @@ So then I'd say, 1329 01:29:05,896 --> 01:29:07,298 -I mean, you could go ahead now +you could go ahead now 1330 01:29:07,298 --> 01:29:11,265 @@ -5340,7 +5340,7 @@ the most important one all right yeah 1336 01:29:28,473 --> 01:29:32,740 -so yeah so this fixes uh or closes +so yeah so this fixes or closes 1337 01:29:32,740 --> 01:29:35,204 @@ -5352,27 +5352,27 @@ an hour issue we'll do some 1339 01:29:37,428 --> 01:29:39,531 -magic then on github +magic then on GitHub 1340 01:29:40,355 --> 01:29:42,819 -let's switch to back to github +let's switch to back to GitHub 1341 01:29:42,819 --> 01:29:43,780 -and we can see here uh +and we can see here 1342 01:29:45,483 --> 01:29:46,825 -when i cloned the when i +when I cloned the when i 1343 01:29:46,825 --> 01:29:49,829 -forked the repository it also copied um +forked the repository it also copied 1344 01:29:49,829 --> 01:29:51,532 -for example all of those github actions +for example all of those GitHub actions 1345 01:29:51,532 --> 01:29:52,613 @@ -5380,7 +5380,7 @@ so you don't need to 1346 01:29:52,613 --> 01:29:55,217 -reset them just because uh +reset them just because 1347 01:29:55,217 --> 01:29:56,259 @@ -5396,7 +5396,7 @@ yeah because those that the ml 1350 01:30:02,909 --> 01:30:05,653 -file is included in the github +file is included in the GitHub 1351 01:30:07,473 --> 01:30:07,653 @@ -5424,7 +5424,7 @@ You don't need to, you set it 1357 01:30:16,583 --> 01:30:18,265 -once and then you kind of +once and then you 1358 01:30:18,265 --> 01:30:19,927 @@ -5456,7 +5456,7 @@ Yeah. 1365 01:30:31,239 --> 01:30:36,585 -So see, we can see success tests have, uh, +So see, we can see success tests have, 1366 01:30:38,354 --> 01:30:38,975 @@ -5488,7 +5488,7 @@ Do I have to be taller? 1373 01:31:07,953 --> 01:31:10,337 -contribute maybe open pull request. +contribute open pull request. 1374 01:31:11,359 --> 01:31:13,423 @@ -5500,7 +5500,7 @@ Let's come back. 1376 01:31:19,434 --> 01:31:22,920 -I guess this, yeah, we will +this, yeah, we will 1377 01:31:22,920 --> 01:31:25,144 @@ -5532,15 +5532,15 @@ And I press refresh. 1384 01:32:01,379 --> 01:32:04,624 -and uh okay it didn't throw up like +and okay it didn't throw up like 1385 01:32:04,624 --> 01:32:06,286 -that but uh with the color +that but with the color 1386 01:32:06,286 --> 01:32:08,429 -but i can see here yeah issues +but I can see here yeah issues 1387 01:32:08,429 --> 01:32:10,713 @@ -5548,7 +5548,7 @@ we have one still then here 1388 01:32:10,713 --> 01:32:14,058 -pull requests one i click here +pull requests one I click here 1389 01:32:14,899 --> 01:32:16,862 @@ -5560,19 +5560,19 @@ fix subtraction fixes error number 1391 01:32:19,205 --> 01:32:24,433 -one or issue number one and uh +one or issue number one and 1392 01:32:24,433 --> 01:32:30,762 -maybe old but i say pound once yeah okay +old but I say pound once yeah okay 1393 01:32:35,905 --> 01:32:38,929 -uh, prove the workflows to run like this. +prove the workflows to run like this. 1394 01:32:41,933 --> 01:32:47,059 -Um, so they actually, you see here, +so they you see here, 1395 01:32:47,059 --> 01:32:47,820 @@ -5584,7 +5584,7 @@ few tests being run here. 1397 01:32:49,081 --> 01:32:51,184 -So, um, what's running here, +So, what's running here, 1398 01:32:51,184 --> 01:32:52,946 @@ -5600,7 +5600,7 @@ set up with the actions. 1401 01:32:57,332 --> 01:33:02,318 -Uh, then here, um, Oh, +then here, Oh, 1402 01:33:03,547 --> 01:33:04,969 @@ -5672,7 +5672,7 @@ That's good news. 1419 01:34:41,923 --> 01:34:43,506 -Yeah, perhaps there was some +Yeah, there was some 1420 01:34:43,506 --> 01:34:48,372 @@ -5680,7 +5680,7 @@ typo when I added it in the Jaml file. 1421 01:34:53,600 --> 01:34:55,262 -I actually think that... +I think that... 1422 01:34:57,149 --> 01:34:58,150 @@ -5732,7 +5732,7 @@ that both the issue and 1434 01:35:31,926 --> 01:35:33,488 -the pull requests are, I mean, +the pull requests are, 1435 01:35:33,488 --> 01:35:34,830 @@ -5740,7 +5740,7 @@ we don't have any open on these. 1436 01:35:36,052 --> 01:35:40,979 -And I actually say, what happened now, +And I say, what happened now, 1437 01:35:40,979 --> 01:35:41,900 @@ -5776,7 +5776,7 @@ don't have clean termination of everything. 1445 01:35:58,709 --> 01:36:02,795 -and uh yeah i do think of course +and yeah I do think of course 1446 01:36:02,795 --> 01:36:03,896 @@ -5792,7 +5792,7 @@ something happens like this here 1449 01:36:07,281 --> 01:36:08,863 -then uh yeah perhaps you +then yeah perhaps you 1450 01:36:08,863 --> 01:36:10,165 @@ -5800,7 +5800,7 @@ could nevertheless go ahead and merge 1451 01:36:11,226 --> 01:36:11,947 -as long as you know what +as long as what 1452 01:36:11,947 --> 01:36:13,890 @@ -5808,11 +5808,11 @@ you're doing and then you might 1453 01:36:13,890 --> 01:36:19,738 -then get back to it and then next day um +then get back to it and then next day 1454 01:36:20,900 --> 01:36:25,226 -great um we could perhaps we +great we could perhaps we 1455 01:36:25,226 --> 01:36:27,068 @@ -5936,7 +5936,7 @@ aware of that this can happen. 1485 01:48:12,586 --> 01:48:14,369 -so with that i think we +so with that I think we 1486 01:48:14,369 --> 01:48:17,354 @@ -5956,15 +5956,15 @@ so this comes also with 1490 01:48:29,273 --> 01:48:32,017 -an exercise that's uh which you +an exercise that's which you 1491 01:48:32,017 --> 01:48:34,140 -will also spend uh at least +will also spend at least 1492 01:48:34,140 --> 01:48:39,569 -well say 20 minutes with um it's mostly about +well say 20 minutes with it's mostly about 1493 01:48:39,569 --> 01:48:42,192 @@ -6004,7 +6004,7 @@ The first five or so are 1502 01:49:01,991 --> 01:49:04,113 -sort of on the simpler side. +on the simpler side. 1503 01:49:04,113 --> 01:49:08,037 @@ -6020,7 +6020,7 @@ the exercise that you start with 1506 01:49:12,383 --> 01:49:13,745 -a simple one and then maybe +a simple one and then 1507 01:49:15,187 --> 01:49:16,670 @@ -6036,7 +6036,7 @@ Yeah, so there are, I 1510 01:49:21,577 --> 01:49:23,079 -won't maybe go through all of +won't go through all of 1511 01:49:23,079 --> 01:49:27,485 @@ -6096,7 +6096,7 @@ that you're writing interfaces with 1525 01:50:01,364 --> 01:50:02,986 -some kind of hardware, for +some hardware, for 1526 01:50:02,986 --> 01:50:04,608 @@ -6296,7 +6296,7 @@ since we're already quite late. 1575 02:12:07,136 --> 02:12:11,304 -So next would be, we'll maybe go back. +So next would be, we'll go back. 1576 02:12:11,304 --> 02:12:13,168 @@ -6308,7 +6308,7 @@ now, we've mostly talked about 1578 02:12:14,971 --> 02:12:17,356 -Python and PyTest. +Python and pytest. 1579 02:12:17,356 --> 02:12:20,320 @@ -6328,7 +6328,7 @@ So yeah, let's look at C++. 1583 02:12:27,830 --> 02:12:30,274 -And we'll be using catch2. +And we'll be using Catch2. 1584 02:12:33,538 --> 02:12:36,803 @@ -6368,7 +6368,7 @@ so we need to include these 1593 02:13:17,286 --> 02:13:21,171 -macros that Catch2 provides, like so. +macros that Catch2 provides, so. 1594 02:13:21,171 --> 02:13:25,716 @@ -6412,7 +6412,7 @@ here, the integer test. 1604 02:13:53,924 --> 02:13:57,911 -Maybe, [name], you can maybe +[name], you can 1605 02:13:57,911 --> 02:14:01,517 @@ -6456,7 +6456,7 @@ case, we have the int test. 1615 02:14:38,451 --> 02:14:39,993 -I mean, that's int for integer. +that's int for integer. 1616 02:14:41,295 --> 02:14:41,455 @@ -6488,11 +6488,11 @@ And yeah, so whatever's in there 1623 02:14:59,295 --> 02:15:03,001 -is just a sort of parameter to this macro. +is just a parameter to this macro. 1624 02:15:03,001 --> 02:15:05,585 -um and in this require we +and in this require we 1625 02:15:05,585 --> 02:15:07,708 @@ -6508,7 +6508,7 @@ to this assert that you saw earlier 1628 02:15:10,893 --> 02:15:14,979 -in um in uh pi test so +in in pi test so 1629 02:15:14,979 --> 02:15:17,723 @@ -6516,11 +6516,11 @@ that's that's our code and then 1630 02:15:17,723 --> 02:15:19,866 -um catch two is very integrated +catch two is very integrated 1631 02:15:19,866 --> 02:15:25,555 -with cmake um so we're not +with cmake so we're not 1632 02:15:25,555 --> 02:15:27,037 @@ -6548,7 +6548,7 @@ But yeah, so CMake is 1638 02:15:40,017 --> 02:15:40,938 -in the broadest terms, I guess +in the broadest terms, 1639 02:15:40,938 --> 02:15:43,422 @@ -6564,7 +6564,7 @@ for compiled languages to build 1642 02:15:49,711 --> 02:15:53,677 -and sort of build the binaries or +and build the binaries or 1643 02:15:53,677 --> 02:15:55,279 @@ -6604,7 +6604,7 @@ when you're in conjunction with 1652 02:16:10,313 --> 02:16:14,878 -Catch-2 to run tests, for example. +Catch2 to run tests, for example. 1653 02:16:14,878 --> 02:16:18,922 @@ -6632,7 +6632,7 @@ you build it and whatever that means. 1659 02:16:31,619 --> 02:16:34,723 -So first is some sort of preamble. +So first is some preamble. 1660 02:16:36,004 --> 02:16:38,327 @@ -6648,7 +6648,7 @@ And so you don't need to 1663 02:16:44,676 --> 02:16:46,659 -sort of install it yourself first, +install it yourself first, 1664 02:16:46,659 --> 02:16:49,684 @@ -6656,11 +6656,11 @@ which I have also done, but 1665 02:16:49,684 --> 02:16:51,346 -it's not sort of strictly necessary +it's not strictly necessary 1666 02:16:51,346 --> 02:16:52,668 -because you can sort of put +because you can put 1667 02:16:52,668 --> 02:16:54,130 @@ -6680,7 +6680,7 @@ down here, that is also 1671 02:17:04,586 --> 02:17:08,872 -basically provided or sort of +basically provided or 1672 02:17:08,872 --> 02:17:10,515 @@ -6728,7 +6728,7 @@ that you would need to run the tests 1683 02:17:34,176 --> 02:17:36,580 -and sort of do all of the things +and do all of the things 1684 02:17:36,580 --> 02:17:39,045 @@ -6764,7 +6764,7 @@ the test that we're running. 1692 02:17:55,718 --> 02:17:59,466 -So now, how does one actually run that? +So now, how does one run that? 1693 02:17:59,466 --> 02:18:04,377 @@ -6784,7 +6784,7 @@ In Python, you just run pytest. 1697 02:18:13,113 --> 02:18:16,418 -For catch2, you would need to run this. +For Catch2, you would need to run this. 1698 02:18:17,479 --> 02:18:18,621 @@ -6796,7 +6796,7 @@ too familiar with CMAC. 1700 02:18:19,763 --> 02:18:23,829 -So this will kind of prepare +So this will prepare 1701 02:18:23,829 --> 02:18:26,453 @@ -6820,7 +6820,7 @@ compile the actual executable 1706 02:18:36,612 --> 02:18:38,576 -binaries, like so. +binaries, so. 1707 02:18:39,799 --> 02:18:41,963 @@ -6852,7 +6852,7 @@ that our code is very short, 1714 02:18:55,937 --> 02:18:58,860 -but the catch-2 test, the catch-2 +but the Catch2 test, the Catch2 1715 02:18:58,860 --> 02:19:01,203 @@ -6868,7 +6868,7 @@ more than we are currently asking of it. 1718 02:19:05,829 --> 02:19:07,671 -And yeah, I guess it's +And yeah, it's 1719 02:19:07,671 --> 02:19:09,072 @@ -6916,7 +6916,7 @@ One could also have 1730 02:19:32,731 --> 02:19:33,372 -I mean, you could have +you could have 1731 02:19:33,372 --> 02:19:35,876 @@ -6960,7 +6960,7 @@ Yeah, well, if you would add it here, 1741 02:20:03,090 --> 02:20:08,128 -let's say that example.cc source +that example.cc source 1742 02:20:08,128 --> 02:20:10,236 @@ -7060,7 +7060,7 @@ Yeah. 1766 02:21:06,367 --> 02:21:09,251 -So, uh, since we're already quite late, +So, since we're already quite late, 1767 02:21:09,251 --> 02:21:10,973 @@ -7072,7 +7072,7 @@ for that as well, but I would suggest 1769 02:21:12,855 --> 02:21:16,400 -that we skip that and, uh, +that we skip that and, 1770 02:21:16,400 --> 02:21:20,024 @@ -7080,19 +7080,19 @@ move on to our next point 1771 02:21:20,024 --> 02:21:24,670 -in the agenda, um, which +in the agenda, which 1772 02:21:24,670 --> 02:21:26,573 -is maybe some conclusions. +is some conclusions. 1773 02:21:28,836 --> 02:21:30,618 -Um, yeah. +yeah. 1774 02:21:31,720 --> 02:21:32,040 -Um, + 1775 02:21:33,910 --> 02:21:34,591 @@ -7120,7 +7120,7 @@ a learning curve for these tools. 1781 02:21:57,395 --> 02:21:59,197 -So PyTest, which are mainly +So pytest, which are mainly 1782 02:21:59,197 --> 02:22:03,101 @@ -7152,11 +7152,11 @@ you simply need to... 1789 02:22:20,654 --> 02:22:22,296 -I mean, you need to figure out +you need to figure out 1790 02:22:22,296 --> 02:22:24,859 -for yourself whether, let's say, +for yourself whether, 1791 02:22:24,859 --> 02:22:26,761 @@ -7220,7 +7220,7 @@ I would also point out there, 1806 02:23:03,536 --> 02:23:06,400 -so we used mostly PyTest and +so we used mostly pytest and 1807 02:23:07,562 --> 02:23:08,945 @@ -7228,7 +7228,7 @@ for the most part, it was 1808 02:23:08,945 --> 02:23:11,208 -kind of almost invisible. +almost invisible. 1809 02:23:11,208 --> 02:23:14,474 @@ -7244,7 +7244,7 @@ how you approach them, you may 1812 02:23:17,298 --> 02:23:20,824 -be only used PyTest by calling PyTest. +be only used pytest by calling pytest. 1813 02:23:20,824 --> 02:23:23,428 @@ -7284,15 +7284,15 @@ set the tolerance, which might be 1822 02:23:43,950 --> 02:23:45,011 -sort of a little bit more +a little bit more 1823 02:23:45,011 --> 02:23:49,876 -robust than sort of just checking +robust than just checking 1824 02:23:49,876 --> 02:23:52,418 -sort of the absolute difference +the absolute difference 1825 02:23:52,418 --> 02:23:56,442 @@ -7324,7 +7324,7 @@ And yeah, so there's a little 1832 02:24:11,339 --> 02:24:14,423 -bit more to PyTest than we showed. +bit more to pytest than we showed. 1833 02:24:14,423 --> 02:24:16,005 @@ -7332,7 +7332,7 @@ But yeah, I think the 1834 02:24:16,005 --> 02:24:18,408 -nice thing about PyTest is that it +nice thing about pytest is that it 1835 02:24:18,408 --> 02:24:19,770 @@ -7344,7 +7344,7 @@ smooth on-ramp, very much 1837 02:24:21,632 --> 02:24:26,358 -unlike something like Catch-2. +unlike something like Catch2. 1838 02:24:26,358 --> 02:24:28,260 @@ -7380,15 +7380,15 @@ Yeah. 1846 02:24:42,978 --> 02:24:45,662 -um but yeah and uh i would +but yeah and I would 1847 02:24:45,662 --> 02:24:47,506 -say i i use pytest quite a +say I i use pytest quite a 1848 02:24:47,506 --> 02:24:48,728 -lot and i would uh yeah +lot and I would yeah 1849 02:24:48,728 --> 02:24:50,671 @@ -7400,19 +7400,19 @@ you find a framework that you like 1851 02:24:52,133 --> 02:24:59,686 -and and launch um yeah and +and and launch yeah and 1852 02:24:59,686 --> 02:25:02,691 -uh as we talked about earlier +as we talked about earlier 1853 02:25:02,691 --> 02:25:07,396 -also so i mean your your code is one thing +also so your your code is one thing 1854 02:25:07,396 --> 02:25:09,399 -that you need to, I mean, +that you need to, 1855 02:25:09,399 --> 02:25:10,660 @@ -7432,7 +7432,7 @@ there's always an environment in form of, 1859 02:25:19,551 --> 02:25:20,372 -I mean, running on different +running on different 1860 02:25:20,372 --> 02:25:22,555 @@ -7448,11 +7448,11 @@ And there, a common thing is 1863 02:25:27,561 --> 02:25:31,827 -that then, I mean, you need to +that then, you need to 1864 02:25:31,827 --> 02:25:33,589 -be ready to, to, uh, +be ready to, to, 1865 02:25:35,273 --> 02:25:38,297 @@ -7460,7 +7460,7 @@ to work with the available resources. 1866 02:25:38,297 --> 02:25:40,681 -And I mean, things can happen. +And things can happen. 1867 02:25:40,681 --> 02:25:42,243 @@ -7488,7 +7488,7 @@ some other system. 1873 02:25:59,348 --> 02:26:00,330 -So I mean, in particular +So in particular 1874 02:26:00,330 --> 02:26:02,513 @@ -7500,11 +7500,11 @@ where you have worked through all of, 1876 02:26:05,783 --> 02:26:11,570 -let's say, the more obvious bugs +the more obvious bugs 1877 02:26:11,570 --> 02:26:13,653 -or things that I guess you're wrong +or things that you're wrong 1878 02:26:13,653 --> 02:26:17,578 @@ -7524,7 +7524,7 @@ if the environment changes. 1882 02:26:24,427 --> 02:26:25,789 -Let's say you upgrade your +you upgrade your 1883 02:26:25,789 --> 02:26:28,032 @@ -7608,7 +7608,7 @@ I would also not underestimate 1903 02:27:24,091 --> 02:27:29,800 -the kind of documentation effect testing has. +the documentation effect testing has. 1904 02:27:29,800 --> 02:27:36,991 @@ -7616,7 +7616,7 @@ It can be really useful to see tests 1905 02:27:36,991 --> 02:27:39,815 -and you, well, I guess at +and you, well, at 1906 02:27:39,815 --> 02:27:41,458 @@ -7696,7 +7696,7 @@ Yeah. 1925 02:28:18,217 --> 02:28:21,942 -And here one can naturally, I mean, +And here one can naturally, 1926 02:28:21,942 --> 02:28:23,765 @@ -7716,7 +7716,7 @@ be used like examples. 1930 02:28:31,255 --> 02:28:32,897 -And I mean, examples then also +And examples then also 1931 02:28:32,897 --> 02:28:36,923 @@ -7728,7 +7728,7 @@ Yeah. 1933 02:28:39,887 --> 02:28:43,598 -And that's actually very much +And that's very much 1934 02:28:43,598 --> 02:28:47,282 @@ -7760,7 +7760,7 @@ But it could also be that 1941 02:28:59,975 --> 02:29:01,436 -it's sort of intermixed. +it's intermixed. 1942 02:29:01,436 --> 02:29:03,138 @@ -7804,7 +7804,7 @@ that one main reason why you then, 1952 02:29:30,221 --> 02:29:31,964 -after all, perhaps let's say split, +after all, split, 1953 02:29:33,506 --> 02:29:34,167 @@ -7816,7 +7816,7 @@ say, end-to-end testing, why you 1955 02:29:36,550 --> 02:29:40,433 -have, let's say, distinct set of input files +have, distinct set of input files 1956 02:29:40,433 --> 02:29:44,919 @@ -7836,7 +7836,7 @@ So when you have examples, for a code, 1960 02:29:54,753 --> 02:29:57,157 -you would like to have, let's say, +you would like to have, 1961 02:29:57,157 --> 02:29:58,759 @@ -7848,7 +7848,7 @@ also it's nice if you can 1963 02:30:00,622 --> 02:30:04,066 -have some, let's say, more real use cases. +have some, more real use cases. 1964 02:30:04,066 --> 02:30:07,071 @@ -7912,7 +7912,7 @@ do it a little bit in, so 1979 02:30:48,272 --> 02:30:52,818 -to say, I mean, you can do it in different sizes. +to say, you can do it in different sizes. 1980 02:30:52,818 --> 02:30:54,099 @@ -7924,7 +7924,7 @@ say, the small test suite, and 1982 02:30:57,544 --> 02:30:59,146 -then let's say the large test +then the large test 1983 02:30:59,146 --> 02:31:00,809 @@ -7936,11 +7936,11 @@ run the big thing. 1985 02:31:02,960 --> 02:31:03,845 -I mean, not on a daily +not on a daily 1986 02:31:03,845 --> 02:31:06,217 -basis, but perhaps let's say once +basis, but perhaps once 1987 02:31:06,217 --> 02:31:06,921 @@ -7968,7 +7968,7 @@ And this way, you can sort 1993 02:31:16,407 --> 02:31:19,252 -of select maybe not test everything at once. +of select not test everything at once. 1994 02:31:19,252 --> 02:31:20,334 @@ -7992,7 +7992,7 @@ And these test suites sort 1999 02:31:27,206 --> 02:31:29,069 -of usually provide some kind of +of usually provide some 2000 02:31:29,069 --> 02:31:32,014 @@ -8004,7 +8004,7 @@ Yeah. 2002 02:31:35,287 --> 02:31:37,531 -And maybe some more words just +And some more words just 2003 02:31:37,531 --> 02:31:39,614 @@ -8024,7 +8024,7 @@ you probably have an end-to-end test 2007 02:31:48,949 --> 02:31:50,692 -that you can sort of +that you can 2008 02:31:50,692 --> 02:31:51,834 @@ -8052,7 +8052,7 @@ units of code that are in there 2014 02:32:04,518 --> 02:32:07,304 -sort of if you have structured +if you have structured 2015 02:32:07,304 --> 02:32:08,547 @@ -8064,11 +8064,11 @@ And if you haven't, then that 2017 02:32:11,052 --> 02:32:12,816 -would be kind of maybe a +would be a 2018 02:32:12,816 --> 02:32:14,700 -good sort of inspiration on +good inspiration on 2019 02:32:14,700 --> 02:32:15,642 @@ -8152,7 +8152,7 @@ session to your own workflow 2039 02:33:11,707 --> 02:33:13,970 -and maybe learn something new. +and learn something new. 2040 02:33:13,970 --> 02:33:15,853 @@ -8248,7 +8248,7 @@ which is the place where 2063 02:34:04,224 --> 02:34:06,427 -the Code Refinery community hangs out +the CodeRefinery community hangs out 2064 02:34:06,427 --> 02:34:10,413