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

V3 specs not independent from each other (Deployment and cancelling deployment) #531

Open
renelehmann opened this issue Apr 26, 2022 · 0 comments

Comments

@renelehmann
Copy link

Issue

Tests for "deployments" and "v3" features includes creating and removing of a zip file (staticfile.zip).
If the zip file already/still exists an error on creating the zip file will occur:
"file already exists: assets/staticfile.zip"

Context

cats version: 7.4.0 (against cloudfoundry v19.0.0)
cats.json inlcudes v3 and deployments
running testsuite in parallel (-nodes=x) and without randomize.

The spec "Deployment" and "cancelling deployments" does/could interfere each other on having the same zip file name
which will be created on the "BeforeEach" and removed on the "AfterEach" step.
https://github.com/cloudfoundry/cf-acceptance-tests/blob/v7.4.0/v3/deployment.go.

error on (by creating the zip file if its already/still exists):

Expect(err).NotTo(HaveOccurred())

Possible Fix

Creating dedicated/independent zip filenames for each spec or else.

workaround:

  • Running cats testsuite with "randomizeAllSpecs" will probably help to prevent the situation on interfere of each other but without a guarantee.
  • Running cats testsuite without parallelize (default -node=1).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant