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

Degradation of tests performance in release 0.2.8 #157

Open
lsolovey opened this issue Feb 24, 2022 · 1 comment
Open

Degradation of tests performance in release 0.2.8 #157

lsolovey opened this issue Feb 24, 2022 · 1 comment

Comments

@lsolovey
Copy link

I noticed significant degradation of performance in running our unit tests using 0.2.7 vs 0.2.8. The time increased from ~10 seconds to ~6 minutes.

Is anyone else seeing this as well? Why is there such a big difference?

docker run -ti --rm -v %cd%/myChart:/apps quintush/helm-unittest:3.5.4-0.2.7 --helm3 -o test-output.xml --output-type JUnit /apps

<output omitted>

Charts:      1 passed, 1 total
Test Suites: 91 passed, 91 total
Tests:       250 passed, 250 total
Snapshot:    72 passed, 72 total
Time:        9.8886118s
docker run -ti --rm -v %cd%/myChart:/apps quintush/helm-unittest:3.5.4-0.2.8 --helm3 -o test-output.xml --output-type JUnit /apps

<output omitted>

Charts:      1 passed, 1 total
Test Suites: 91 passed, 91 total
Tests:       250 passed, 250 total
Snapshot:    72 passed, 72 total
Time:        6m7.6379221s
@rquinio1A
Copy link

It might be the reload of the chart under test between each test case: d55debb
I think the problem is that Helm lib is not designed to do more than one rendering (I guess it's not use case the CLI has to support), so they were nasty bugs with original cloning solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants