Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tests/resource/aws_ecs_service: Fix TestAccAWSEcsService_withLaunchTypeFargate for parallelization and configuration updates #6732

Merged
merged 1 commit into from
Dec 5, 2018

Conversation

bflad
Copy link
Contributor

@bflad bflad commented Dec 5, 2018

Previously, it this acceptance test was not parallelized with the other tests and was creating/destroying the AWS resources between each step. This now tests via updates, which verifies that functionality and runs much faster (~300s -> ~100s).

Output from acceptance testing:

--- PASS: TestAccAWSEcsService_basicImport (31.52s)
--- PASS: TestAccAWSEcsService_disappears (20.52s)
--- PASS: TestAccAWSEcsService_healthCheckGracePeriodSeconds (249.26s)
--- PASS: TestAccAWSEcsService_ManagedTags (40.42s)
--- PASS: TestAccAWSEcsService_PropagateTags (76.33s)
--- PASS: TestAccAWSEcsService_Tags (39.68s)
--- PASS: TestAccAWSEcsService_withAlb (250.49s)
--- PASS: TestAccAWSEcsService_withARN (37.60s)
--- PASS: TestAccAWSEcsService_withDaemonSchedulingStrategy (49.10s)
--- PASS: TestAccAWSEcsService_withDaemonSchedulingStrategySetDeploymentMinimum (16.55s)
--- PASS: TestAccAWSEcsService_withDeploymentController_Type_CodeDeploy (355.17s)
--- PASS: TestAccAWSEcsService_withDeploymentMinimumZeroMaximumOneHundred (40.75s)
--- PASS: TestAccAWSEcsService_withDeploymentValues (30.13s)
--- PASS: TestAccAWSEcsService_withEcsClusterName (39.48s)
--- PASS: TestAccAWSEcsService_withFamilyAndRevision (35.50s)
--- PASS: TestAccAWSEcsService_withIamRole (177.26s)
--- PASS: TestAccAWSEcsService_withLaunchTypeEC2AndNetworkConfiguration (56.07s)
--- PASS: TestAccAWSEcsService_withLaunchTypeFargate (112.72s)
--- PASS: TestAccAWSEcsService_withLbChanges (277.71s)
--- PASS: TestAccAWSEcsService_withPlacementConstraints (24.62s)
--- PASS: TestAccAWSEcsService_withPlacementConstraints_emptyExpression (30.15s)
--- PASS: TestAccAWSEcsService_withPlacementStrategy (119.51s)
--- PASS: TestAccAWSEcsService_withRenamedCluster (52.67s)
--- PASS: TestAccAWSEcsService_withReplicaSchedulingStrategy (28.76s)
--- PASS: TestAccAWSEcsService_withServiceRegistries (211.01s)
--- PASS: TestAccAWSEcsService_withServiceRegistries_container (201.62s)
--- PASS: TestAccAWSEcsService_withUnnormalizedPlacementStrategy (40.50s)

…peFargate for parallelization and configuration updates

Previously, it this acceptance test was not parallelized with the other tests and was creating/destroying the AWS resources between each "step". This now tests via updates, which verifies that functionality and runs much faster (~300s -> ~100s).

Output from acceptance testing:

```
--- PASS: TestAccAWSEcsService_basicImport (31.52s)
--- PASS: TestAccAWSEcsService_disappears (20.52s)
--- PASS: TestAccAWSEcsService_healthCheckGracePeriodSeconds (249.26s)
--- PASS: TestAccAWSEcsService_ManagedTags (40.42s)
--- PASS: TestAccAWSEcsService_PropagateTags (76.33s)
--- PASS: TestAccAWSEcsService_Tags (39.68s)
--- PASS: TestAccAWSEcsService_withAlb (250.49s)
--- PASS: TestAccAWSEcsService_withARN (37.60s)
--- PASS: TestAccAWSEcsService_withDaemonSchedulingStrategy (49.10s)
--- PASS: TestAccAWSEcsService_withDaemonSchedulingStrategySetDeploymentMinimum (16.55s)
--- PASS: TestAccAWSEcsService_withDeploymentController_Type_CodeDeploy (355.17s)
--- PASS: TestAccAWSEcsService_withDeploymentMinimumZeroMaximumOneHundred (40.75s)
--- PASS: TestAccAWSEcsService_withDeploymentValues (30.13s)
--- PASS: TestAccAWSEcsService_withEcsClusterName (39.48s)
--- PASS: TestAccAWSEcsService_withFamilyAndRevision (35.50s)
--- PASS: TestAccAWSEcsService_withIamRole (177.26s)
--- PASS: TestAccAWSEcsService_withLaunchTypeEC2AndNetworkConfiguration (56.07s)
--- PASS: TestAccAWSEcsService_withLaunchTypeFargate (112.72s)
--- PASS: TestAccAWSEcsService_withLbChanges (277.71s)
--- PASS: TestAccAWSEcsService_withPlacementConstraints (24.62s)
--- PASS: TestAccAWSEcsService_withPlacementConstraints_emptyExpression (30.15s)
--- PASS: TestAccAWSEcsService_withPlacementStrategy (119.51s)
--- PASS: TestAccAWSEcsService_withRenamedCluster (52.67s)
--- PASS: TestAccAWSEcsService_withReplicaSchedulingStrategy (28.76s)
--- PASS: TestAccAWSEcsService_withServiceRegistries (211.01s)
--- PASS: TestAccAWSEcsService_withServiceRegistries_container (201.62s)
--- PASS: TestAccAWSEcsService_withUnnormalizedPlacementStrategy (40.50s)
```
@bflad bflad requested a review from a team December 5, 2018 20:26
@ghost ghost added size/XS Managed by automation to categorize the size of a PR. service/ecs Issues and PRs that pertain to the ecs service. tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure. labels Dec 5, 2018
Copy link
Member

@mbfrahry mbfrahry left a comment

Choose a reason for hiding this comment

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

LGTM!

@bflad bflad added this to the v1.51.0 milestone Dec 5, 2018
@bflad bflad merged commit 3e2a870 into master Dec 5, 2018
@bflad bflad deleted the t-aws_ecs_service-fargate-paralleltest branch December 5, 2018 20:51
@ghost
Copy link

ghost commented Apr 2, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
service/ecs Issues and PRs that pertain to the ecs service. size/XS Managed by automation to categorize the size of a PR. tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants