flutter/docs
Matan Lurey 9e273d5e6e
Remove scenario_app/android and rename to ios_scenario_app. (#160992)
🚫 **BLOCKED** : Do not merge until
https://github.com/flutter/flutter/issues/161261 (additional test
coverage).

---

This PR eliminates (1) `scenario_app/android`, and all references to an
Android `scenario_app`, including documentation, CI configuration, build
rules, test runner, Android-side test application, and (2), to verify
and disambiguate the remains, renames the folder `ios_scenario_app`,
which is now accurate.

It also eliminates elements that were _only_ used in the Android-side
scenario_app, such as Firebase Test Lab uploading.

I would be open to doing this in phases if we thought it was better to
do so, but given its mostly a mechanical change (and by renaming the
directory, references can be checked merely by looking for
`/\bscenario_app/`, I believe this is safe to iterate on and eventually
merge after the holidays.

## Background

As of the merged mono-repo, there is no longer a requirement for the
engine to be testable as a standalone unit.

As an example,
[`%ENGINE%/testing/scenario_app`](3762f2e973/engine/src/flutter/testing/scenario_app),
which was intended to _emulate_ the Flutter framework (and some of
`flutter_tools` tooling), load the iOS and Android embedder, and run
various "scenarios" (which ran a combination of `dart:ui` code and
Android Java/iOS Obj-C) verifying golden-file screenshots.

Instead, it is now possible to write and run _real_ (full) Flutter apps
the same way that an end-user (or our own tests) would. One such example
is
[`dev/native_driver_test`](https://github.com/flutter/flutter/tree/master/dev/integration_tests/native_driver_test),
which is a full-fledged Flutter app, which uses standard tooling (i.e.
`flutter`), to test most of the same elements that previously were only
tested in the Android version of `scenario_app`.
2025-01-28 03:43:46 +00:00
..
about We no longer have a separate engine repo. (#161400) 2025-01-10 02:37:29 +00:00
contributing [Release] Update the cherry-pick process. (#161771) 2025-01-17 15:44:31 +00:00
ecosystem Fixed typos (#159331) 2024-12-05 16:54:09 +00:00
examples [wiki migration] Leftover wiki pages and links (#148989) 2024-05-28 15:12:10 +00:00
infra Prettier merge_queue.md (#158969) 2024-11-18 19:32:23 +00:00
libraries/material [wiki migration] Framework team pages (#148721) 2024-05-20 23:40:35 +00:00
platforms Remove scenario_app/android and rename to ios_scenario_app. (#160992) 2025-01-28 03:43:46 +00:00
postmortems Misc docs cleanup and fixes (#155501) 2024-09-24 20:03:08 +00:00
releases Fix link to hotfix documentation best practices (#162116) 2025-01-24 15:17:48 +00:00
roadmap [wiki migration] Leftover wiki pages and links (#148989) 2024-05-28 15:12:10 +00:00
tool docs: Rework "Making changes to the flutter tool" to include flutter-dev (#157480) 2024-10-23 23:28:57 +00:00
triage Update two_dimensional_scrollables triage routing (#161667) 2025-01-15 19:14:33 +00:00
wiki_archive Misc docs cleanup and fixes (#155501) 2024-09-24 20:03:08 +00:00
Flutter-Self-Service-Index.md Misc docs cleanup and fixes (#155501) 2024-09-24 20:03:08 +00:00
In-case-of-emergency.md Misc docs cleanup and fixes (#155501) 2024-09-24 20:03:08 +00:00
README.md Misc docs cleanup and fixes (#155501) 2024-09-24 20:03:08 +00:00

This wiki is primarily aimed at engineers building or making contributions to Flutter.

If you are new to Flutter, then you will find more general information on the Flutter project, including tutorials and samples, on our website at flutter.dev. For specific information about Flutter's APIs, consider our API reference which can be found at the api.flutter.dev.

If you want to know what we're likely to do in the future, our roadmap may be of interest.

If you intend to contribute to Flutter, welcome! You are encouraged to start with our contributor guide, which helps onboard new team members. It points to the most relevant pages on this wiki. You are also invited to join our Discord server.

Index of notable sections