c9b132d079
Adds the ability to rename Runner.xcodeproj and Runner.xcworkspace - fixes https://github.com/flutter/flutter/issues/9767. To rename a project: 1. Open Runner.xcodeproj in Xcode 2. In the left panel, left click "Show File Inspector" <img width="441" alt="Screenshot 2023-04-17 at 11 41 07 PM" src="https://user-images.githubusercontent.com/36148254/232692957-8743742d-c3ef-42e5-833f-dff31aeb2b6a.png"> 3. In the right panel, the name of the project, "Runner", should be visible under "Identity and Type". Change the name and press enter. <img width="299" alt="Screenshot 2023-04-17 at 11 40 43 PM" src="https://user-images.githubusercontent.com/36148254/232693315-b6a71165-f5e3-4a0f-8954-2f3eee5b67cf.png"> 4. A wizard should pop up. Click Rename. <img width="573" alt="Screenshot 2023-04-17 at 11 44 01 PM" src="https://user-images.githubusercontent.com/36148254/232693381-bb9cf026-2a75-4844-b42d-ae0036ae9fdd.png"> To rename the workspace: 1. Make sure Xcode is closed. 2. Rename the .xcworkspace to your new name. If you also renamed the project 3. Reopen the .xcworkspace in Xcode. If the selected project is the old name and in red, update it to match the new project name. Tests for schemeFor were changed as with Xcode 14, in some cases the scheme will be renamed along with the project. Thus we will get the best match scheme for either the project name, or the default name Runner. However if a flavor is present, the scheme should always match the flavor.
This directory contains tests for specific flutter commands.
Tests that are self-contained unit tests should go in hermetic/.
Tests that are more end-to-end, e.g. that involve actually running
subprocesses, should go in permeable/.
The ../../tool/coverage_tool.dart script (which is used to collect
coverage for the tool) runs only the tests in the hermetic directory
when collecting coverage.