Problem/Motivation
- For AWS, we have the following videos to explain how to use AWS Cloud (AWS Cloud portal):
- a. Create the resources for Acceptance Test
- b. EC2 Instance Overview
- c. Create SSH Keys
- d. Import AMI Images
- e. Create Launch Templates
- f. Launch EC2 Instances
- Create an acceptance tests based on each video
- The basic sequence is:
- As an IT admin, I want to log into the site so that I can see or access~.
- As an IT admin, I want to add an AWS Cloud service provider named
AWS BDD. <- Hard-coded is fine for now because this string is specifically used for Behat. - As an IT admin, I wan to create a role named
BDD Rolethat contains the access permissions to the AWS Cloud service providerAWS BDDand view own instance. - As an IT admin, I want to create a test user named
bdd_userwith the permissionBDD Role - As a user, I want to log into the site so that I can see or access~.
- As a user, I want to launch an instance named
bdd_instance. - As a user, I want to view the instance
bdd_instanceso that s/he can confirm . - As a user, I want to terminate the instance
bdd_instanceso that s/he cannot access to the instance. - As an IT admin, I want to delete the AWS Cloud. service provider
AWS BDDso that~ - As an IT admin, I want to delete the permission
BDD Roleso that~ - As an IT admin, I want to delete the user
bdd_userso that~
Issue fork cloud-3229497
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3229497-Create-the-resources-for-Acceptance-Test
changes, plain diff MR !416
Comments
Comment #4
yutong.li commentedComment #5
yutong.li commentedComment #6
yasComment #7
yutong.li commentedComment #9
yutong.li commentedComment #10
yutong.li commentedComment #11
yutong.li commentedComment #12
yas@yutong.li
Thank you for the update. It looks good now, and I want to have the further request for you to refactor the password portion for the future expansion for the flexibility. Could you please take a look at it? Thanks!
Comment #13
yutong.li commentedComment #14
yas@yutong.li
Thank you for the update. It looks good to me now. I'll merge the patch to
4.xand close this issue as Fixed.Comment #15
yas@yutong.li
I found one thing that we should parameterized. Could you please check my comment above? Thanks!
Comment #16
yutong.li commentedComment #17
yasComment #18
yutong.li commentedComment #19
yutong.li commented@yas
I opened another ticket to "align naming convention". I will be working on that on a different branch.
Comment #20
yas@yutong.li
Thank you for the update. This patch looks pretty good now. I feel
test/src/Behatcan be moved tomodules/cloud_service_provider/aws_cloud/test/src/Behatsince this patch aimsaws_cloudmodule.What do you think?
Comment #21
yutong.li commented@yas
I think we can keep behat scenarios at the current location for now.
Currently under
tests/src/Behat, some tests are NOT aws-specific. Such generic tests should stay at the current directory, and aws-specific ones will be moved tomodules/cloud_service_provider/aws_cloud/test/src/Behateventually.At this moment, we are migrating the test env to the new QA env. Once I become comfortable with the new env, then we can move aws-specific scenarios to the new location.
Comment #22
yutong.li commented@yas
I reorganized the behat files according to your suggestion. Thanks:)
Comment #23
yas@yutong.li
Thank you for the update and making your great efforts. The patch looks perfect now. I'll merge the patch to
4.xand close this issue as Fixed.Comment #24
yasComment #27
yas