Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-49263

Determine minimal useful test case for running ATH for Jenkins Core

        [JENKINS-49263] Determine minimal useful test case for running ATH for Jenkins Core

        Two failures in 85 executions, the frequency has decreased even more but is still flaky and the same error... I am starting to wonder that this may be a real bug instead of a test problem...

        Raul Arabaolaza added a comment - Two failures in 85 executions, the frequency has decreased even more but is still flaky and the same error... I am starting to wonder that this may be a real bug instead of a test problem...

        Given the amount of integration testing related to security and login I am going to dedicate only today to this test, if I am not able to properly fix it (may it be a race condition on the UI, something related to how Jenkins notifies of login events, or a cache problem) my proposal will be to eliminate the test from the SmokeTest category   

        Raul Arabaolaza added a comment - Given the amount of integration testing related to security and login  I am going to dedicate only today to this test, if I am not able to properly fix it (may it be a race condition on the UI, something related to how Jenkins notifies of login events, or a cache problem) my proposal will be to eliminate the test from the SmokeTest category   

        Raul Arabaolaza added a comment - - edited

        Confirmed that I have not been able to remove the flakiness of JenkinsDatabaseSecurityRealmTest#login_and_logout in a reasonable amount of time, so my proposal is to remove it from the `SmokeTest` category, create a ticket to try to fix it properly and add it again when fixed

        Raul Arabaolaza added a comment - - edited Confirmed that I have not been able to remove the flakiness of JenkinsDatabaseSecurityRealmTest#login_and_logout in a reasonable amount of time, so my proposal is to remove it from the `SmokeTest` category, create a ticket to try to fix it properly and add it again when fixed

        ScriptTest and SlaveTest have not shown flakiness in my runs, BUT they have shown some lack of robustness against changes in the UI in the history, so is better to remove them from the list for the first implementation

        Raul Arabaolaza added a comment - ScriptTest and SlaveTest have not shown flakiness in my runs, BUT they have shown some lack of robustness against changes in the UI in the history, so is better to remove them from the list for the first implementation

        So my proposal is to run the SmokeTest Category "fixed" by #PR-410

        Raul Arabaolaza added a comment - So my proposal is to run the SmokeTest Category "fixed" by #PR-410

        Code changed in jenkins
        User: Raul Arabaolaza
        Path:
        src/test/java/core/JenkinsDatabaseSecurityRealmTest.java
        http://jenkins-ci.org/commit/acceptance-test-harness/3413c9ffc7093d014cf81327832d97545adfbf0c
        Log:
        JENKINS-49263 Remove login test from SmokeTest until is fixed

        SCM/JIRA link daemon added a comment - Code changed in jenkins User: Raul Arabaolaza Path: src/test/java/core/JenkinsDatabaseSecurityRealmTest.java http://jenkins-ci.org/commit/acceptance-test-harness/3413c9ffc7093d014cf81327832d97545adfbf0c Log: JENKINS-49263 Remove login test from SmokeTest until is fixed

        Code changed in jenkins
        User: Raul Arabaolaza
        Path:
        src/test/java/core/ScriptTest.java
        http://jenkins-ci.org/commit/acceptance-test-harness/f07816a49d38c7416e20865f02bebe76eb6fd467
        Log:
        JENKINS-49263 Remove ScriptTest from SmokeTest

        • As it has shown symptoms of lack of robustness

        SCM/JIRA link daemon added a comment - Code changed in jenkins User: Raul Arabaolaza Path: src/test/java/core/ScriptTest.java http://jenkins-ci.org/commit/acceptance-test-harness/f07816a49d38c7416e20865f02bebe76eb6fd467 Log: JENKINS-49263 Remove ScriptTest from SmokeTest As it has shown symptoms of lack of robustness

        Code changed in jenkins
        User: Raul Arabaolaza
        Path:
        src/test/java/core/SlaveTest.java
        http://jenkins-ci.org/commit/acceptance-test-harness/9098f4a8e368fe3daa3db98691781fdc10d9a459
        Log:
        JENKINS-49263 Remove SlaveTest from SmokeTest

        • AS it has shown symptoms of lack of robustness

        SCM/JIRA link daemon added a comment - Code changed in jenkins User: Raul Arabaolaza Path: src/test/java/core/SlaveTest.java http://jenkins-ci.org/commit/acceptance-test-harness/9098f4a8e368fe3daa3db98691781fdc10d9a459 Log: JENKINS-49263 Remove SlaveTest from SmokeTest AS it has shown symptoms of lack of robustness

        Code changed in jenkins
        User: Oliver Gondža
        Path:
        src/test/java/core/JenkinsDatabaseSecurityRealmTest.java
        src/test/java/core/ScriptTest.java
        src/test/java/core/SlaveTest.java
        http://jenkins-ci.org/commit/acceptance-test-harness/bdef2c394483ad7d530060ee2227162c3e285b10
        Log:
        Merge pull request #410 from raul-arabaolaza/JENKINS-49263

        JENKINS-49263 Remove flaky and no robust enough tests from SmokeTest Category

        SCM/JIRA link daemon added a comment - Code changed in jenkins User: Oliver Gondža Path: src/test/java/core/JenkinsDatabaseSecurityRealmTest.java src/test/java/core/ScriptTest.java src/test/java/core/SlaveTest.java http://jenkins-ci.org/commit/acceptance-test-harness/bdef2c394483ad7d530060ee2227162c3e285b10 Log: Merge pull request #410 from raul-arabaolaza/ JENKINS-49263 JENKINS-49263 Remove flaky and no robust enough tests from SmokeTest Category

        No comments against using the SmokeTest so closing this now

        Raul Arabaolaza added a comment - No comments against using the SmokeTest so closing this now

          rarabaolaza Raul Arabaolaza
          rtyler R. Tyler Croy
          Votes:
          0 Vote for this issue
          Watchers:
          4 Start watching this issue

            Created:
            Updated:
            Resolved: