# General introduction to Unity Test Framework > Try out some of Unity Test Framework's core features through general examples. Each exercise in this course is accompanied by a sample project and corresponding solution, which you can import from the Package Manager window. Welcome to the Unity Test Framework general introduction course. This course consists of different exercises to help you learn fundamental Unity Test Framework concepts through practical examples. Each exercise has a **Learning Objectives** section to help you identify the skills you will learn. The exercises are grouped thematically, and their difficulty varies. After completing an exercise, you can check your solution against the one provided. Note that many of the exercises can be solved in several possible ways. ## Import samples Project files for each exercise and its accompanying solution are provided as samples with the Unity Test Framework package. To import an exercise or solution to your Unity Editor: 1. Go to **Window > Package Manager** and, in the [packages list view](https://docs.unity3d.com/Manual/upm-ui-list.html), selct Unity Test Framework. 2. In the package [details view](https://docs.unity3d.com/Manual/upm-ui-details.html), find the **Samples** section. 3. Find the exercise or solution you want to import and click the import button. **The Package Manager window with the expanded list of package samples available for import.:** ![](/api/media?file=/engine/6000.5/media/images/samples.png) > **Note:** > > You can import an exercise and its solution or multiple exercises at the same time, but since several of the exercises use the same naming pattern this will likely result in compilation errors that prevent you running tests or building your project. The recommended workflow is to import and work on one exercise at a time. If you import additional exercises or solutions for reference, you can delete them again before running your main exercise. ## Course outline | **Topic** | **Description** | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **[Running a test in a Unity project](/engine/6000.5/manual/scripting/test-framework-introduction/overview/general-introduction/running-test.md)** | Set up a simple Unity project with a test assembly and tests and run them from the **Test Runner** window. | | **[Arrange, act, assert](/engine/6000.5/manual/scripting/test-framework-introduction/overview/general-introduction/arrange-act-assert.md)** | Use the core unit testing principle of AAA (Arrange, Act, Assert) to structure your unit tests. | | **[Semantic test assertion](/engine/6000.5/manual/scripting/test-framework-introduction/overview/general-introduction/semantic-test-assertion.md)** | Use `Assert.That` to test whether conditions are true. | | **[Custom comparison](/engine/6000.5/manual/scripting/test-framework-introduction/overview/general-introduction/custom-comparison.md)** | Use the Unity Test Framework's custom equality comparers to check for value equality of Unity types. | | **[Asserting logs](/engine/6000.5/manual/scripting/test-framework-introduction/overview/general-introduction/asserting-logs.md)** | Test and verify code that writes to the console log. | | **[Setup and teardown](/engine/6000.5/manual/scripting/test-framework-introduction/overview/general-introduction/setup-teardown.md)** | Use the NUnit attributes `[SetUp]` and `[TearDown]` to reduce code duplication in your tests. | | **[Play mode tests](/engine/6000.5/manual/scripting/test-framework-introduction/overview/general-introduction/play-mode-tests.md)** | Create and run Play mode tests. | | **[Play mode tests in a player](/engine/6000.5/manual/scripting/test-framework-introduction/overview/general-introduction/play-mode-tests-in-player.md)** | Run Play mode tests in a standalone platform Player. | | **[Using the UnityTest attribute](/engine/6000.5/manual/scripting/test-framework-introduction/overview/general-introduction/unitytest-attribute.md)** | Use the `[UnityTest]` to write tests that run across multiple frames. | | **[Long-running tests](/engine/6000.5/manual/scripting/test-framework-introduction/overview/general-introduction/long-running-tests.md)** | Write long-running tests that can instruct the Editor to wait for a defined period of time. | | **[Scene-based tests](/engine/6000.5/manual/scripting/test-framework-introduction/overview/general-introduction/scene-based-tests.md)** | Test content that is stored in a scene. | | **[Setup and cleanup at build time](/engine/6000.5/manual/scripting/test-framework-introduction/overview/general-introduction/build-setup-cleanup.md)** | Perform work before and after the Player build phase. | | **[Domain reload](/engine/6000.5/manual/scripting/test-framework-introduction/overview/general-introduction/domain-reload.md)** | Invoke and wait for domain reload from your tests. | | **[Preserve test state](/engine/6000.5/manual/scripting/test-framework-introduction/overview/general-introduction/preserve-test-state.md)** | Make data in your tests survive domain reloads using serialization. | | **[Test cases](/engine/6000.5/manual/scripting/test-framework-introduction/overview/general-introduction/test-cases.md)** | Work with NUnit's `[TestCase]` attribute in Unity tests. | | **[Custom attributes](/engine/6000.5/manual/scripting/test-framework-introduction/overview/general-introduction/custom-attributes.md)** | Implement custom NUnit attributes, which can be used to alter test execution. | | **[Running tests programmatically](/engine/6000.5/manual/scripting/test-framework-introduction/overview/general-introduction/running-tests-programmatically.md)** | Run tests from code using the [TestRunnerAPI](https://docs.unity3d.com/Packages/com.unity.test-framework@latest/index.html?subfolder=/api/UnityEditor.TestTools.TestRunner.Api.TestRunnerApi.html). | ## Additional resources * [Testing Lost Crypt](/engine/6000.5/manual/scripting/test-framework-introduction/overview/lost-crypt-introduction.md)