 In this screencast, I'm going to be showing you how you can create your own tests. Creating your own test is going to be very useful for Assignment 2 and 3. Now remember that Assignment 2 and Assignment 3 use a bunch of user space programs to do most of the testing. These programs can be found on the user line test menu. As you can see, there's quite a few programs here. Although in Assignment 2, we only use a subset of these. To know exactly which programs we used for testing Assignment 2, you can look at the Assignment 2 target file. Alright, to create your own test, first you create a directory with the same name as the test. In my example, I'm going to create one called myTest. Once this is done, you copy files from an existing test into your new directory. Now, you modify the make file to change the name of the program and the sources that are going to be compiled as part of this program. So I'm going to call this myTest and I'm going to rename this to myTest.c. Once this is done, we also need to change the name of the source file to reflect what we inserted into the make file. So we do that. Now, all that needs to be done is change the, modify the content of the source file to reflect whatever you want to test. In this case, I'm just going to do something as simple as print a hello world. So I'm going to get rid of all of this code and replace it with a simple. Now, by default, the OS 161 GCC has a W error flag enabled, which complains W warning flag enabled, I'm sorry, which complains when you have unused variables. So we're going to get rid of these two variables as well. Save the file and do a B make. As you can see, B make completed successfully. And if I do a B make install, this test will be installed in my root directory. Now, unfortunately, there is one additional step that needs to be done to make sure that this test is compiled every time when you do a B make in the root OS 161 directory. To do that, you go into test bin and modify the make file in there. As you can see here, it defines all the various directories into which the root B make has to go and run a B make. So what we're going to do here is we're going to add our test here. And now we should, if we run a B make here, it will compile our test as well. So this is how you create your own test inside OS 161.