1

00:00:01,390 --> 00:00:05,920

So if you looked at the updated test files that I posted to the last lecture, you will have noticed



2

00:00:05,920 --> 00:00:10,440

that I made some additional changes that I didn't actually mention and they're very straightforward.



3

00:00:10,600 --> 00:00:16,570

So what I did was I took all of those tests where things were done manually one step at a time, and



4

00:00:16,570 --> 00:00:22,750

I turned them into table tests, just like the one you see right here where I define the variable reservation



5

00:00:22,750 --> 00:00:28,930

tests, I describe the struct and then I have the content one test for each row in that particular struct.



6

00:00:29,230 --> 00:00:32,520

And I did it for pretty much all of the tests in this file.



7

00:00:32,890 --> 00:00:37,810

And the reason I did that is that once you figured out how to write a test, chances are you are going



8

00:00:37,810 --> 00:00:42,370

to write tests as table test because it's so much cleaner and you have a lot less code.



9

00:00:42,850 --> 00:00:45,400

So you shouldn't see anything too complex in here.



10

00:00:45,910 --> 00:00:49,390

All of the tests themselves remain, you know, functionally the same.



11

00:00:49,600 --> 00:00:51,580

They're just changed to table tests.



12

00:00:51,760 --> 00:00:55,540

And it makes things a lot simpler to just add a new test.



13

00:00:55,540 --> 00:01:00,750

I just add a row to this struct and you just go on and write additional tests as necessary.



14

00:01:01,240 --> 00:01:05,350

So hopefully this makes sense to you and hopefully you understand how table tests work.



15

00:01:05,650 --> 00:01:11,020

And I do recommend you use them whenever you possibly can because it just generates less code and it



16

00:01:11,020 --> 00:01:13,000

makes it easier to update your tests.