Original subtitles

In the last video we learned about the setup method and how it can be used to execute some code before

each test.

And in addition to setup there are some other test lifecycle methods that we should know about.

And this diagram represents the various metals that we could have inside the TEST file.

So if we want we can write a number of tests which are all different but then we can add a setup method.

And this contains code that is executed before each test.

And we have seen a good example of that in the previous video where we have set the default locale for

our date for mounting tests and then we can have a third down method which runs after each test.

And this is normally used to dispose of some of the resources that were used during the test and then

we also had set up all and tear down all metals which are only executed once before and after all the

tests.

So if you were to run a test file that contains this method this is the order in which each method will

be called First of all we would get a call to set up all and then we would get set up test 1 and third

down and this pattern would be repeated for each test and after third down is called for the last test

then tear down all its gold as well.

And as we make progress we will see some examples using these test metals but for now the key takeaway

is that you can use setup tear down set up all and tell them all to execute some common code that you

would otherwise have to repeat inside each test body and these hubs skipping your tests organized.

OK.

So let's continue on the next video.