Last updated February 6, 2020

In the tutorial, Implement a Functional Test, we learned how to tell BrowserTestBase to use the Standard installation profile in order to get our test passing and letting the Standard profile implicitly provide our dependencies. We also mentioned that doing so probably wasn't the best decision and that we should explicitly declare those dependencies in some way.

In this tutorial, we'll will walk through explicitly declaring those dependencies. When in doubt, it's generally considered a best practice to be as explicit about the dependencies of our tests as possible. By the end of this tutorial, you should be able to:

  • Understand why we want to explicitly declare our dependencies.
  • Determine what the dependencies really are and make a list of them.
  • Implement each dependency in our list.
  • Emerge with a thorough, passing test.