Skip to content
This repository was archived by the owner on Feb 25, 2025. It is now read-only.

Conversation

@arbreng
Copy link
Contributor

@arbreng arbreng commented Aug 10, 2022

Migrate the integration test to CFv2 via using the "Test UI Stack". Eliminates the implicit, unversioned deps between the test and UI package names+routes.

Fixes: https://bugs.fuchsia.dev/p/fuchsia/issues/detail?id=101032

@arbreng arbreng marked this pull request as draft August 10, 2022 20:02
@arbreng arbreng force-pushed the integration-test-cfv2 branch 2 times, most recently from c707fd4 to 795917e Compare August 10, 2022 23:48
@arbreng
Copy link
Contributor Author

arbreng commented Aug 10, 2022

This will pass once https://fuchsia-review.googlesource.com/c/fuchsia/+/710565 and https://fuchsia-review.googlesource.com/c/fuchsia/+/710235 land and roll

PTAL for now, disregarding compilation errors on the bots. Will land once SDK contains the FIDLs

@arbreng arbreng requested a review from akbiggs August 10, 2022 23:53
@arbreng arbreng marked this pull request as ready for review August 10, 2022 23:53
@arbreng arbreng requested a review from shivesh-ganju August 10, 2022 23:53
@arbreng arbreng changed the title [fuchsia] WIP integration test on test-ui-stack [fuchsia] Convert integration test to CFv2 Aug 10, 2022
Copy link
Contributor

@akbiggs akbiggs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wow awesome.


```shell
$ cd "$FUCHSIA_DIR"
$ fx set terminal.x64
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

jw why terminal instead of workstation_eng? I think Fuchsia is trying to converge on workstation being the image for OOT testing in the longer-term.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I used that b/c the Flutter CQ bot currently uses terminal. When we switch the flutter CQ to use workstation_eng we could update this to match. Do you have a bug I can reference in a TODO here?

(Ran the tests locally against workstation_eng and they passed there too FWIW)

$ fx build
```

## Build the test
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I might be wrong but it feels like the build and run test parts could be encapsulated in a build_and_run_test.sh script that takes the name of the integration test folder to run. There might be a switch statement that chooses what package names to publish based on the name of the integration test folder, but besides that it feels the same from test to test.

It feels like it would be a more convenient workflow to do something like:

$ENGINE_DIR/tools/fuchsia/devshell/build_and_run_test.sh flutter-embedder-test

And have it build, publish everything we need and then run the test.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will write this and update instructions

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FWIW I did not get a chance to write this @akbiggs Can we file a bug and push a follow-up CL for it?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No worries! fxb/107344

@arbreng arbreng force-pushed the integration-test-cfv2 branch from 795917e to adbde89 Compare August 11, 2022 01:20
@arbreng arbreng force-pushed the integration-test-cfv2 branch from adbde89 to 31601bf Compare August 19, 2022 20:51
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants