Skip to content
This repository has been archived by the owner on Dec 7, 2023. It is now read-only.

Write e2e test cases for ignite rm #392

Closed
chanwit opened this issue Sep 4, 2019 · 2 comments
Closed

Write e2e test cases for ignite rm #392

chanwit opened this issue Sep 4, 2019 · 2 comments
Assignees
Labels
area/testing Issues related to improving testing
Milestone

Comments

@chanwit
Copy link
Member

chanwit commented Sep 4, 2019

No description provided.

@stealthybox
Copy link
Contributor

Depends on CI /w nested virt

Can accomplish with TravisCI as of recent changes: https://twitter.com/_AkihiroSuda_/status/1167336407779557376

Could also use GCP or AWS vm's spawned from CircleCI, but this would be more latent.

@chanwit chanwit added this to the v0.6.1 milestone Sep 10, 2019
@chanwit chanwit added the area/testing Issues related to improving testing label Sep 10, 2019
@chanwit chanwit self-assigned this Sep 10, 2019
@chanwit chanwit modified the milestones: v0.6.1, v0.7.0 Sep 14, 2019
@bbros-dev
Copy link

We have a test cookbook setup with test-kitchen harness in which it would be simple to write e2e test cases.

I believe these could have avoided a lot of the existing broken/undocumented behavior.

The issue is the cost of firing them up using cloud providers - currently Digital Ocean - everytime the CI/CD prcess runs. Of course this ensures behavior isn't broken as well as no regressions are introduced.

As soon as I port the current test to use JASON manfest rather than YAML it's status will 1.0-rc1.

Happy to join Monday's call if you want to discuss further

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/testing Issues related to improving testing
Projects
None yet
Development

No branches or pull requests

3 participants