Skip to content

Commit

Permalink
Use setup step
Browse files Browse the repository at this point in the history
  • Loading branch information
kenzieschmoll committed Oct 2, 2023
1 parent bf1adbe commit 102574e
Show file tree
Hide file tree
Showing 3 changed files with 25 additions and 3 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ parallel to your `flutter` repository checkout, then, from this
directory, run:

```
pushd ../flutter/dev/customer_testing && pub get && popd
pushd ../flutter/dev/customer_testing && flutter pub get && popd
../flutter/bin/cache/dart-sdk/bin/dart ../flutter/dev/customer_testing/run_tests.dart --skip-template --verbose registry/*.test
```

Expand Down
4 changes: 2 additions & 2 deletions registry/flutter_devtools.test
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ [email protected]
fetch=git clone https://github.com/kenzieschmoll/devtools.git tests
fetch=git -C tests checkout 0729b72c95993e88e57c991d250c0858ee329e78

test.linux=./tool/refresh.sh >> output.txt
setup.linux=./tool/refresh.sh >> output.txt

update=packages/devtools_app
update=packages/devtools_app_shared
Expand All @@ -14,7 +14,7 @@ update=packages/devtools_shared
update=packages/devtools_test

test.linux=./tool/flutter_customer_tests/analyze.sh
#test.linux=./tool/flutter_customer_tests/flutter_customer_tests.sh
test.linux=./tool/flutter_customer_tests/flutter_customer_tests.sh

# Reduce number of iterations because these tests take longer than our recommended maximum.
iterations=1
22 changes: 22 additions & 0 deletions registry/template.test
Original file line number Diff line number Diff line change
Expand Up @@ -63,6 +63,28 @@ [email protected]
fetch=git clone https://github.com/USERNAME/REPOSITORY.git tests
fetch=git -C tests checkout 0123456789abcdef0123456789abcdef01234567

# The "setup" lines specify commands to run before the "update" or
# "test" lines are handled. This is useful for things like generating
# mocks before running the "update" and "test" steps.
#
# Commands specified using "setup=" must work identically on Windows,
# macOS, and Linux. This generally means you want to limit yourself to
# simple commands. For anything more elaborate, consider creating a
# "setup.sh" shell script to run on macOS and Linux and a "setup.bat"
# batch file to run on Windows (referencing it without the extension
# here should mean that in runs the shell script on Unix systems and
# the batch file on Windows, because of how Windows looks up commands).
# On Windows, these commands are executed via
# `CMD.EXE /S /C "command..."`.
#
# Alternatively, you can use a platform-specific test line:
# setup.windows= to run a command on Windows only.
# setup.macos= to run a command on MacOS only.
# setup.linux= to run a command on Linux only.
# setup.posix= to run a command on MacOS and Linux only.
setup.posix=setup.sh
setup.windows=setup.bat

# The "update" lines specify paths (relative to the newly created
# "tests" directory) in which to run a flutter command to
# automatically update the code to fix breaking changes. The command
Expand Down

0 comments on commit 102574e

Please sign in to comment.