Skip to content

cleanup test resources #3693

Open
Open

Description

@DaanHoogland

This is to clean-up tests that create resources and do not clean-up after themselves. The idea is that the entire test-suite should be able to be run in a production environment without harming or messing up. In smoke tests running in Trillian we found the following tests to leave stuff around (the checks fixed in scope of this pr are just for simulator):

ISSUE TYPE
  • Bug Report
  • Other: test improvements

Activity

  1. yadvr commented on Aug 12, 2020

    @yadvr
    Member

    @DaanHoogland is this still valid or can be closed?

  2. DaanHoogland commented on Sep 18, 2020

    @DaanHoogland
    ContributorAuthor

    no @rhtyd , it is still very valid. It is also limited to simulator tests and should be expanded to all tests. I will expand on this the coming weeks (given 4.15 is not asking more attention)

  3. added this to the 4.16.0.0 milestone on Jan 29, 2021
  4. nvazquez commented on Jul 27, 2021

    @nvazquez
    Contributor

    @DaanHoogland is this still valid?

  5. DaanHoogland commented on Jul 27, 2021

    @DaanHoogland
    ContributorAuthor

    yes it is, there is a lot of antiquated code in the smoke tests still, as they are all fixed/passing it is low priority.

  6. DaanHoogland commented on Jul 27, 2021

    @DaanHoogland
    ContributorAuthor

    also it has been touched since a year ago, so removing the 1year old label

  7. yadvr commented on Aug 9, 2021

    @yadvr
    Member

    Maybe review/close or update this issue @DaanHoogland ?

  8. DaanHoogland commented on Aug 17, 2021

    @DaanHoogland
    ContributorAuthor

    @rhtyd @nvazquez this will be open for a long time unless it's getting priority, which it won't as it concerned data and entities being left around in test environments when running smoke tests. I've updated the list and am addressing some for component tests and will address any further I encounter during other work.
    Maybe there should be a milestone "ongoing" or something?

  9. 29 remaining items

  10. added this to the 4.22.1 milestone on Nov 12, 2025
  11. added theissue type on Jan 5, 2026
  12. modified the milestones: 4.22.1, 4.23.0 on Jan 5, 2026
  13. moved this from Done to In Progress in Apache CloudStack 4.22.1on Jan 7, 2026
  14. github-actions commented on May 8, 2026

    @github-actions

    This issue is stale because it has been open for 120 days with no activity. It may be removed by administrators of this project at any time. Remove the stale label or comment to request for removal of it to prevent this.

  15. modified the milestones: 4.23.0, 4.24.0 on Jun 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions