This Unity Editor Extensions allows you to select the viewing direction for a SceneView with the Blender -like hotkeys.
e.g. Numpad 1/3/7 as switch front/right/top view. Numpad 5 as toggle orthographic projection.
This document describes a Mob plugin for IntelliJ IDEs. It includes details like the plugin ID, name, vendor, and a description. It defines an action to start a Mob session from within IntelliJ. It also defines a project settings configurable to configure Mob settings.
This document contains notes from an ATEC meeting on May 26, 2011. The agenda items included discussing JUnit, the Android testing framework, and Android mocking. It provides details on different types of Android test cases like AndroidTestCase and ActivityInstrumentationTestCase2. It also covers how to use mocks in Android tests to isolate dependencies and make tests less fragile. Private methods and fields are discussed as challenges for testing. The benefits of using mocks to avoid dependencies on actual classes are explained.
This document summarizes notes from an ATEC meeting on May 26, 2011. It discusses using JUnit for Android testing, including different types of test cases like AndroidTestCase and ActivityInstrumentationTestCase2. It also covers challenges like testing private methods and fragile tests due to dependencies on implementation details. Mocking libraries and APIs is presented as a solution to make tests less brittle against code changes. The document advocates for using mocks to isolate tests from Android framework classes and external dependencies.
This Unity Editor Extensions allows you to select the viewing direction for a SceneView with the Blender -like hotkeys.
e.g. Numpad 1/3/7 as switch front/right/top view. Numpad 5 as toggle orthographic projection.
This document describes a Mob plugin for IntelliJ IDEs. It includes details like the plugin ID, name, vendor, and a description. It defines an action to start a Mob session from within IntelliJ. It also defines a project settings configurable to configure Mob settings.
This document contains notes from an ATEC meeting on May 26, 2011. The agenda items included discussing JUnit, the Android testing framework, and Android mocking. It provides details on different types of Android test cases like AndroidTestCase and ActivityInstrumentationTestCase2. It also covers how to use mocks in Android tests to isolate dependencies and make tests less fragile. Private methods and fields are discussed as challenges for testing. The benefits of using mocks to avoid dependencies on actual classes are explained.
This document summarizes notes from an ATEC meeting on May 26, 2011. It discusses using JUnit for Android testing, including different types of test cases like AndroidTestCase and ActivityInstrumentationTestCase2. It also covers challenges like testing private methods and fragile tests due to dependencies on implementation details. Mocking libraries and APIs is presented as a solution to make tests less brittle against code changes. The document advocates for using mocks to isolate tests from Android framework classes and external dependencies.