Now one of the biggest benefits of test driven development or test?
Well, the test suit in general is that you can use it as a documentation.
So if you want to see how a method behaves, you can simply open up the tests and read them.
So your tests are like a living up to date documentation.
And in fact, what's written inside of the test even proves that it does what it claims.
So let's open up the Test explorer one more time right here.
Well, and you can see that I'm not sure why those are not tested yet, but once we start them and let
them pass, it's totally fine.
You can simply go through all of that.
Right.
And check the methods and check what the functionality of that application is.
And that's really awesome.
And you even as I said, have a proof that it really does what it claims.
So for example, like the flight, let's open it up.
We got some flight specifications and you can see, okay, our application avoids overbooking.
Well, we check or we know that the booking reduces the number of seats in the flight.
Then we check if a flight gets booked successfully.
We also check if we free up the seats when we cancel a booking.
Again, we also check for doesn't cancel bookings for passengers who have not booked.
Right.
So there are really a lot of scenarios that we are testing there and it really gives us a great idea
of what our application is doing right now.
And even if some other software developers would come to your project, they would have an incredible
valuable source of information and proof.
So for example, in application test, what do we have right here?
If we open it up, we can see, okay, remember it's bookings, which is also nice.
So we know, okay, our application remembers what bookings we have inside of a database, for example,
and we free them up.
And all of that is tested.
So your test suit that we got right here, all of your written tests are really like a living documentation
of your program.