Skip to content

Conversation

@nturgut
Copy link
Contributor

@nturgut nturgut commented Feb 19, 2020

Description

We would like to add a simple smoke test which uses Flutter web engine and a Flutter app.

Steps before merging the PR:

Then we can add a task that looks like this to Cirrus:

dart dev/webdriver_test.dart &
flutter drive --target=test_driver/scroll_perf_web.dart -d web-server --release --browser-name=chrome

Related Issues

Tests

This PR only includes only test code.

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I signed the CLA.
  • I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
  • I read the Tree Hygiene wiki page, which explains my responsibilities.
  • I updated/added relevant documentation (doc comments with ///).
  • All existing and new tests are passing.
  • The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
  • I am willing to follow-up on review comments in a timely manner.

Breaking Change

Did any tests fail when you ran them? Please read Handling breaking changes.

  • No, no existing tests failed, so this is not a breaking change.
  • Yes, this is a breaking change. If not, delete the remainder of this section.

@nturgut nturgut requested a review from yjbanov February 19, 2020 00:13
@fluttergithubbot fluttergithubbot added d: examples Sample code and demos c: contributor-productivity Team-specific productivity, code health, technical debt. labels Feb 19, 2020
@nturgut
Copy link
Contributor Author

nturgut commented Feb 20, 2020

Waiting for another PR to land before merging this test.

.cirrus.yml Outdated
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we reuse the web_integration_tests shard?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It is very different as the content goes. Especially with the template. May be I am missing something. What is the advantage if we use it? We should also change/remove the template from that shard then.

Copy link
Contributor

Choose a reason for hiding this comment

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

A smoke test is an integration test. It's just a simple integration test. So I thought it belonged in the integration test shard. We also probably don't want too many shards as they all run simultaneously and occupy machines. I imagine eventually we'll have a hundred integration tests, and we'll shard them into N shards as we see fit, similarly to what we do with widget tests. This way we don't have hand-maintained specialized shards.

@nturgut nturgut merged commit 9ba4eb0 into flutter:master Feb 24, 2020
import 'package:flutter/widgets.dart';

void main() => runApp(const Center(child: Text('Hello, world!', textDirection: TextDirection.ltr)));
void main() =>
Copy link
Contributor

Choose a reason for hiding this comment

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

Could you open a new PR to revert this change?

Copy link
Contributor

Choose a reason for hiding this comment

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

It adds a key to the Text widget, which is needed by the test.

Copy link
Contributor Author

@nturgut nturgut Feb 25, 2020

Choose a reason for hiding this comment

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

Why are we reverting the change? The test are passing. I checked the smoke test after the PR went in. It always passed. Build was also green after my change according to the dashboard.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

c: contributor-productivity Team-specific productivity, code health, technical debt. d: examples Sample code and demos

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants