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

Rename e2e -> integration_test #2918

Merged
merged 26 commits into from
Aug 19, 2020
Merged

Rename e2e -> integration_test #2918

merged 26 commits into from
Aug 19, 2020

Conversation

dnfield
Copy link
Contributor

@dnfield dnfield commented Aug 10, 2020

The e2e name is not entirely fitting for this plugin - some of our consumers expect e2e to implement larger multi-system tests exercising both client and server, which makes this package confusing. Adding the word test also should make this package more discoverable on pub for users looking for test packages.

WIP while I figure out which other plugin(s) need bumps to accomodate pubspec changes.

@dnfield dnfield added the WIP label Aug 10, 2020
@dnfield dnfield marked this pull request as ready for review August 13, 2020 06:54
@dnfield
Copy link
Contributor Author

dnfield commented Aug 13, 2020

The lint failure is because it's looking for a URL that doesn't exist yet, since this PR will be creating that URL.

@dnfield
Copy link
Contributor Author

dnfield commented Aug 13, 2020

/cc @csells

@dnfield
Copy link
Contributor Author

dnfield commented Aug 13, 2020

/cc @jiahaog as this will impact the internal roll/naming.

Copy link
Contributor

@digiter digiter left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Member

@jiahaog jiahaog left a comment

Choose a reason for hiding this comment

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

Thanks, I will take care of the roll internally

@@ -2,7 +2,7 @@
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.

package dev.flutter.plugins.e2e;
package dev.flutter.plugins.integrationTest;
Copy link
Member

Choose a reason for hiding this comment

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

I believe package names should only be in all lowercase characters a-z characters where possible

https://docs.oracle.com/javase/tutorial/java/package/namingpkgs.html

@@ -1,3 +1,3 @@
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="dev.flutter.e2e">
package="dev.flutter.integration_test">
Copy link
Member

Choose a reason for hiding this comment

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

Should integration_test match the package of the Java sourcs?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ahh good catch, I'll make this match up.

@mklim
Copy link
Contributor

mklim commented Aug 14, 2020

I don't see an obvious way that the previously existing e2e package on pub would be linked to the new name from this PR, is that a concern? I think it would probably help to keep e2e as an empty package in the repo and publish a README update about the rename to pub, but I'm not really familiar with all the context here.

@dnfield
Copy link
Contributor Author

dnfield commented Aug 14, 2020

That's a good idea. I was going to just locally modify e2e for that

import 'package:path/path.dart' as path;

/// This method remains for backword compatibility.
Future<void> main() => e2eDriver();
Future<void> integration_main() => integrationDriver();
Copy link
Contributor

@CareF CareF Aug 14, 2020

Choose a reason for hiding this comment

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

If we are not calling it main anyway, why not just remove it? I was thinking if it's main it automatically can be used as a driver script. And keep it main can avoid breaking change to user's test.

@CareF
Copy link
Contributor

CareF commented Aug 14, 2020

And there's e2e in root directory readme.md.

@dnfield
Copy link
Contributor Author

dnfield commented Aug 14, 2020

@CareF I've updated the READMe. I'm not calling it main so you can import it without an alias more easily and still use it.

@CareF
Copy link
Contributor

CareF commented Aug 16, 2020

I'm not calling it main so you can import it without an alias more easily and still use it.

I get that, but I mean Future<void> integration_main() => integrationDriver(); this is no longer necessary if we don't want a main here. Users can directly use integrationDriver in their driver file.

@dnfield
Copy link
Contributor Author

dnfield commented Aug 17, 2020

This is currently blocked by apparently unrelated timeouts on infra. Trying to open another PR to shard.

@dnfield dnfield removed the WIP label Aug 18, 2020
@dnfield
Copy link
Contributor Author

dnfield commented Aug 19, 2020

Red CI is because this PR creates a directory the CI is checking for.

Landing on red for that reason. If this goes red on post submit will revert.

@dnfield dnfield merged commit 89794a6 into flutter:master Aug 19, 2020
@dnfield dnfield deleted the rename_e2e branch August 19, 2020 18:48
jarrodcolburn pushed a commit to jarrodcolburn/plugins that referenced this pull request Aug 20, 2020
* e2e -> integration_test and associated version bumps
jorgefspereira pushed a commit to jorgefspereira/plugins_flutter that referenced this pull request Oct 10, 2020
* e2e -> integration_test and associated version bumps
FlutterSu pushed a commit to FlutterSu/flutter-plugins that referenced this pull request Nov 20, 2020
* e2e -> integration_test and associated version bumps
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants