You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I realised that for ALE, a lot of tests could run faster if some set up and tear down code only runs once for each file. After spending some time trying to think of names for blocks like that which are self-explanatory, I came up with BeforeFirst and AfterLast. These would be analogous to setUpClass and tearDownClass for Python unit test classes.
You could use AfterLast to clean up data from a Before block, if you know you set up some data before every test, but only have to remove it after all of the tests have been run.
I realised that for ALE, a lot of tests could run faster if some set up and tear down code only runs once for each file. After spending some time trying to think of names for blocks like that which are self-explanatory, I came up with
BeforeFirst
andAfterLast
. These would be analogous tosetUpClass
andtearDownClass
for Python unit test classes.You could use both types of block together.
You could use
AfterLast
to clean up data from aBefore
block, if you know you set up some data before every test, but only have to remove it after all of the tests have been run.The text was updated successfully, but these errors were encountered: