hashgraph / hashgraph/full-stack-testing
GMD: Refactor tests used to run faster and prevent timeouts
- 主要语言
- Java
- 星标
- 9
- 派生
- 3
- PR 合并指标
- 30 天内没有已合并 PR
描述
Deepak received the following error when running locally:
```
20:44:03.123 [main] DEBUG org.gradle.internal.remote.internal.inet.TcpOutgoingConnector -- Attempting to connect to [c2216a24-0828-48ce-8d33-2a4c4a18aaa1 port:52134, addresses:[/127.0.0.1]].
20:44:03.127 [main] DEBUG org.gradle.internal.remote.internal.inet.TcpOutgoingConnector -- Trying to connect to address /127.0.0.1.
20:44:03.135 [main] DEBUG org.gradle.internal.remote.internal.inet.TcpOutgoingConnector -- Connected to address /127.0.0.1:52134.
> Task :fullstack-gradle-plugin:test
20:44:03.158 [main] DEBUG org.gradle.process.internal.worker.child.ActionExecutionWorker -- Starting Gradle Test Executor 6.
20:44:03.162 [Test worker] INFO org.gradle.api.internal.tasks.testing.worker.TestWorker -- Gradle Test Executor 6 started executing tests.
> Task :fullstack-gradle-plugin:test
com.hedera.fullstack.gradle.plugin.HelmInstallChartTaskTest
✔ test an error is thrown when the chart is not found
- Helm Install Chart Task for Hedera Network Chart
> Task :fullstack-helm-client:test
Helm Client Tests
Parameterized Chart Installation with Options Executes Successfully
✘ [1] Atomic Chart Installation Executes Successfully (10s)
java.util.concurrent.TimeoutException: testChartInstallOptions(com.hedera.fullstack.helm.client.test.HelmClientTest$ChartInstallOptionsTestParameters, com.jcovalent.junit.logging.LoggingOutput) timed out after 10 seconds
✔ [2] Install Chart with Combination of Options Executes Successfully
✔ [3] Install Chart with Dependency Updates
✔ [4] Install Chart with Description
✔ [5] Install Chart with DNS Enabled
✔ [6] Forced Chart Installation (5.1s)
✘ [7] Install Chart with Password (10s)
java.util.concurrent.TimeoutException: testChartInstallOptions(com.hedera.fullstack.helm.client.test.HelmClientTest$ChartInstallOptionsTestParameters, com.jcovalent.junit.logging.LoggingOutput) timed out after 10 seconds
✘ [8] Install Chart From Repository (10s)
java.util.concurrent.TimeoutException: testChartInstallOptions(com.hedera.fullstack.helm.client.test.HelmClientTest$ChartInstallOptionsTestParameters, com.jcovalent.junit.logging.LoggingOutput) timed out after 10 seconds
✔ [9] Install Chart Skipping CRDs
✔ [10] Install Chart with Timeout
✔ [11] Install Chart with Username (6.4s)
✘ [12] Install Chart with Specific Version (10s)
java.util.concurrent.TimeoutException: testChartInstallOptions(com.hedera.fullstack.helm.client.test.HelmClientTest$ChartInstallOptionsTestParameters, com.jcovalent.junit.logging.LoggingOutput) timed out after 10 seconds
✘ [13] Install Chart with Wait (10s)
java.util.concurrent.TimeoutException: testChartInstallOptions(com.hedera.fullstack.helm.client.test.HelmClientTest$ChartInstallOptionsTestParameters, com.jcovalent.junit.logging.LoggingOutput) timed out after 10 seconds
```
贡献指南
调研方向
Start by running the fullstack-helm-client tests and reading HelmClientTest, especially ChartInstallOptionsTestParameters and the timed-out cases shown in the report. Trace how those parameterized tests perform chart installation and identify what can be refactored to avoid the 10-second timeouts; done means the affected tests complete reliably without timeouts and the suite runs faster.
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- helm, java
- 领域
- testing-qa
- Issue 类型
- 重构
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 35/100