Respository for the I/O 2019 demo: Become a tech lead, slay bugs, and don't get fired.
Developer Quest
Become a tech lead, slay bugs, and don't get fired.
All in Flutter.
Research tree
The game progression is based on a "research tree" of tasks. The tree is defined in codein lib/src/shared_state/task_tree
but for clarity it is also kept as a diagramin assets/docs
. Here's the PNG.

Performance testing
Attach a real device and run the following command from the root of the repo:
shflutter drive --target=test_driver/performance.dart --profile
This will do an automated run-through of the app, and will save the output to files.
- Look into to
build/walkthrough-*.json
files for detailed summaries of each run. - Look at
test_driver/perf_stats.tsv
to compare latest runs with historical data. - Run
Rscript test_driver/generate-graphs.R
(assuming you have R installed) to generateboxplots of the latest runs. This will show up as test_driver/*.pdf
files. - Peruse the raw data file (used by R to generate the boxplots) by opening the
durations.tsv
file. These files contain build and rasterization times for each framefor every run.
If you want to get several runs at once, you can use something like the following command:
shDESC="my change" bash -c 'for i in {1..5}; do flutter drive --target=test_driver/performance.dart --profile; sleep 1; done'
Why run several times when we get so many data points on each walkthrough? With several identicalwalkthroughs it's possible to visually check variance between runs. Even with box plots,these nuances get lost in the summary stats, so it's hard to see whether a change actuallybrought any performance improvement or not. Running several times also eliminatesthe effect of extremely bad luck, like for example when Android decides to update some app whiletest is running.
Lock CPU and GPU speed for your performance test device
Run the following command when your performance test device is attached via USB.
bash./tool/lock_android_scaling.sh
WARNING:
Where to store the profiling data
You probably don't want to check the *.tsv
output files into the repo. For that,run git update-index --assume-unchanged test_driver/*.tsv
in the root dir. This is a one timecommand per machine.
To restore the repository download the bundle
wget https://archive.org/download/github.com-2d-inc-developer_quest_-_2019-07-02_05-00-41/2d-inc-developer_quest_-_2019-07-02_05-00-41.bundle
and run:
git clone 2d-inc-developer_quest_-_2019-07-02_05-00-41.bundle
Source:
https://github.com/2d-inc/developer_questUploader:
2d-incUpload date: 2019-07-02