Problem/Motivation

Write a BDD test suite to make sure no resources are listed after adding OpenStack cloud service provider

  • The purpose of this scenario is to make sure all the resources from the previous test run are deleted correctly and the test starts with a clean state
  • Unlike AWS, some resources need to be created outside C.O., this ticket is only to make sure there are no resources created through the previous BDD tests

Issue fork cloud-3332132

Command icon 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:

About issue forks

Comments

TamakiFujino created an issue. See original summary.

TamakiFujino opened merge request !1520

TamakiFujino’s picture

TamakiFujino commented
Status: Active » Needs review
TamakiFujino’s picture

TamakiFujino commented

@yas I moved the scenarios to confirm the permission setting to 01-03 file since it is not required to operate every single time.

yas made their first commit to this issue’s fork.

yas’s picture

yas
🇯🇵 he/him
Primary language Japanese
Location California 🇺🇸
commented
Title: Add a BDD test suite for checking all the OpenStack resources are at the clean state after adding cloud service provider » Add a BDD test suite for checking all the OpenStack resources are at the clean state after adding an OpenStack cloud service provider
Status: Needs review » Reviewed & tested by the community

@tamakifujino

Thank you for adding the test scenario. I ran the BDD tests and the tests have been passed successfully. I'll merge the patch to 4.x and 5.x, and close this issue as Fixed.

  • yas committed 6e2c2ae2 on 5.x authored by TamakiFujino 
    Issue #3332132 by TamakiFujino, yas: Add a BDD test suite for checking...

  • yas committed 50578c37 on 4.x authored by TamakiFujino 
    Issue #3332132 by TamakiFujino, yas: Add a BDD test suite for checking...
yas’s picture

yas
🇯🇵 he/him
Primary language Japanese
Location California 🇺🇸
commented
Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.