[
https://issues.apache.org/jira/browse/SCB-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anant Dahiya updated SCB-2692:
------------------------------
Description:
Flaky JUnit Tests identified in foundations/foundation-vertx
*How did we detect Flaky Test ?*
We detected the existence of flaky test using the tool
[NonDex|https://github.com/TestingResearchIllinois/NonDex]
mvn -pl foundations/foundation-vertx
edu.illinois:nondex-maven-plugin:1.1.2:nondex
-Dtest=org.apache.servicecomb.foundation.vertx.http.TestAbstractHttpServletRequest#testAttribute
*Tests :*
|foundations/foundation-vertx|org.apache.servicecomb.foundation.vertx.http.TestAbstractHttpServletRequest.testAttribute|
|foundations/foundation-vertx|org.apache.servicecomb.foundation.vertx.http.TestStandardHttpServletRequestEx.parameterMap_merge|
|foundations/foundation-vertx|org.apache.servicecomb.foundation.vertx.http.TestStandardHttpServletRequestEx.setParameter|
|foundations/foundation-vertx|org.apache.servicecomb.foundation.vertx.http.TestVertxServerRequestToHttpServletRequest.setParameter|
was:
Flaky JUnit Tests in foundations/foundation-vertx
*What are flaky tests :*
[LINK|https://www.techtarget.com/whatis/definition/flaky-test]
*How did we detect Flaky Test ?*
We detected the existence of flaky test using the tool
[NonDex|https://github.com/TestingResearchIllinois/NonDex]
*Why we should flaky tests?*
Flaky tests are one of the biggest hurdles in maintaining a reliable test
automation framework.
Flaky tests are expensive to debug: engineering teams invest days, weeks, and
sometimes months of effort to isolate the problem for root-cause analysis.
Even if the reaction is to rerun the test and hope it won’t fail again, that’s
still time lost for every failure (involving manual intervention to review,
decide to re-run and make the decision to ignore it if the second run passes).
*Tests :*
|foundations/foundation-vertx|org.apache.servicecomb.foundation.vertx.http.TestAbstractHttpServletRequest.testAttribute|
|foundations/foundation-vertx|org.apache.servicecomb.foundation.vertx.http.TestStandardHttpServletRequestEx.parameterMap_merge|
|foundations/foundation-vertx|org.apache.servicecomb.foundation.vertx.http.TestStandardHttpServletRequestEx.setParameter|
|foundations/foundation-vertx|org.apache.servicecomb.foundation.vertx.http.TestVertxServerRequestToHttpServletRequest.setParameter|
Summary: junit flaky tests in foundations/foundation-vertx (was: JUNIT
Flaky Tests)
> junit flaky tests in foundations/foundation-vertx
> -------------------------------------------------
>
> Key: SCB-2692
> URL: https://issues.apache.org/jira/browse/SCB-2692
> Project: Apache ServiceComb
> Issue Type: Bug
> Affects Versions: java-chassis-2.7.0
> Reporter: Anant Dahiya
> Priority: Major
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Flaky JUnit Tests identified in foundations/foundation-vertx
>
> *How did we detect Flaky Test ?*
> We detected the existence of flaky test using the tool
> [NonDex|https://github.com/TestingResearchIllinois/NonDex]
>
> mvn -pl foundations/foundation-vertx
> edu.illinois:nondex-maven-plugin:1.1.2:nondex
> -Dtest=org.apache.servicecomb.foundation.vertx.http.TestAbstractHttpServletRequest#testAttribute
>
> *Tests :*
> |foundations/foundation-vertx|org.apache.servicecomb.foundation.vertx.http.TestAbstractHttpServletRequest.testAttribute|
> |foundations/foundation-vertx|org.apache.servicecomb.foundation.vertx.http.TestStandardHttpServletRequestEx.parameterMap_merge|
> |foundations/foundation-vertx|org.apache.servicecomb.foundation.vertx.http.TestStandardHttpServletRequestEx.setParameter|
> |foundations/foundation-vertx|org.apache.servicecomb.foundation.vertx.http.TestVertxServerRequestToHttpServletRequest.setParameter|
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
