When executing multi-threaded, what way can dependent methods and ordinary methods be executed under the same thread?

[Jinglong233]

public class TestclassSample {

  @Test
  public void dependsOnMethods() {
    System.out.println("dependsOnMethods");
  }
  
  @Test(dependsOnMethods = "dependsOnMethods")
  public void test2() {
    System.out.println("test2");
  }
}

How to ensure that dependsOnMethods and test2 are executed under the same thread when multi-threaded execution

[krmahadevan]

@Jinglong233 - Please run with this JVM argument enabled : -Dtestng.thread.affinity=true That should do the trick

[krmahadevan]

Also please ensure you are using the latest version.

[Jinglong233]

Thank you for your answer, it has been solved

[Jinglong233]

@krmahadevan By using the-Dtestng.thread.affinity=true parameter, the problem mentioned above is indeed solved.
But I encountered a new problem: using parallel="classes", when the number of threads is less than the number of test classes. He prioritizes execution of all dependent methods, but my scenario is highly dependent on the current thread. For example, thread 1 executes test class A, thread 2 executes test class 2, and they must execute all test cases in the corresponding class. Only after resources are released can the thread execute other test classes.
Now: Thread 1 has executed the dependent method in test class A, Thread 1

[Jinglong233]

@krmahadevan

@Slf4j
public class ZK_JXB_Index_DownloadTestCase extends BaseTest {
    @Test
    public void switch_ZKCJGL_ZK_JXB_Index_DownloadTestCase() {
        log.info("switch_ZKCJGL_ZK_JXB_Index_DownloadTestCase " + Thread.currentThread().getName());

    }


    @Test(priority = 1, groups = "ZK_JXB_Index_Button_Download",dependsOnMethods = {"switch_ZKCJGL_ZK_JXB_Index_DownloadTestCase"})
    public void download_PLDCJXB() {
        log.info("download_PLDCJXB "  + Thread.currentThread().getName());
    }
}

@Slf4j
public class ZK_JXB_PopUp_DownloadTestCase extends BaseTest {



    @Test
    public void switch_ZKCJGL_ZK_JXB_PopUp_DownloadTestCase() {
        log.info("switch_ZKCJGL_ZK_JXB_PopUp_DownloadTestCase " + Thread.currentThread().getName());

    }


    @Test(priority = 1, groups = "ZK_JXB_PopUp_Button_Download",dependsOnMethods = {"switch_ZKCJGL_ZK_JXB_PopUp_DownloadTestCase"})
    public void download_LRQKDC() {
        log.info("download_LRQKDC " + Thread.currentThread().getName());

    }
    

}

@Slf4j
public class ZK_JXB_Stu_DownloadTestCase extends BaseTest {



    @Test
    public void switch_ZKCJGL_ZK_JXB_Stu_DownloadTestCase() {
        log.info("switch_ZKCJGL_ZK_JXB_Stu_DownloadTestCase " + Thread.currentThread().getName());
    }


    @Test(priority = 1, groups = "ZK_JXB_Index_Button_Download",dependsOnMethods = {"switch_ZKCJGL_ZK_JXB_Stu_DownloadTestCase"})
    public void download_DC() {
        log.info("download_DC " + Thread.currentThread().getName());
    }


}

@Slf4j
public abstract class BaseTest {

    @BeforeClass
    public void setUp() {
        Manager.initThreadResources();
    }
    @AfterClass
    public void tearDown() {
        Manager.closeThreadResources();
    }




    @BeforeSuite
    public void beforeSuite() {
            log.info("beforeSuite ：" + Thread.currentThread().getName());
    }





    @AfterSuite
    public void afterSuite() {
        log.info("afterSuite ：" + Thread.currentThread().getName());
    }
}

@Slf4j
public class Manager {



    public static void initThreadResources() {
        log.info(Thread.currentThread().getName() + " initThreadResources");
    }



    public static void closeThreadResources() {
        log.info(Thread.currentThread().getName() + " closeThreadResources");
    }

}

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "https://testng.org/testng-1.0.dtd">
<suite name="Parallel Suite" parallel="instances" thread-count="2">
    <test name="Test Execution">

        <classes>
            <class name="com.jl.zk.zk_JXB.download.ZK_JXB_Index_DownloadTestCase"></class>
            <class name="com.jl.zk.zk_JXB.download.ZK_JXB_PopUp_DownloadTestCase"></class>
            <class name="com.jl.zk.zk_JXB.download.ZK_JXB_Stu_DownloadTestCase"></class>
        </classes>
    </test>
</suite>

The result of his execution is this：

[INFO ] 
beforeSuite ：main
[INFO ] 
TestNG-test-Test Execution-1 initThreadResources
[INFO ] 
TestNG-test-Test Execution-2 initThreadResources
[INFO ] 
switch_ZKCJGL_ZK_JXB_PopUp_DownloadTestCase TestNG-test-Test Execution-2
[INFO ] 
switch_ZKCJGL_ZK_JXB_Index_DownloadTestCase TestNG-test-Test Execution-1
[INFO ] 
TestNG-test-Test Execution-1 initThreadResources
[INFO ] 
switch_ZKCJGL_ZK_JXB_Stu_DownloadTestCase TestNG-test-Test Execution-1
[INFO ] 
download_LRQKDC TestNG-test-Test Execution-2
[INFO ] 
download_PLDCJXB TestNG-test-Test Execution-1
[INFO ] 
TestNG-test-Test Execution-1 closeThreadResources
[INFO ] 
TestNG-test-Test Execution-2 closeThreadResources
[INFO ] 
download_DC TestNG-test-Test Execution-1
[INFO ] 
TestNG-test-Test Execution-1 closeThreadResources
[INFO ] 
afterSuite ：main

===============================================
Parallel Suite
Total tests run: 6, Passes: 6, Failures: 0, Skips: 0
===============================================

I hope that after TestNG-test-Test Execution-1 has executed all the test cases within one class, it releases the resources (closeThreadResources) and then proceeds to execute the content within another class.
The current problem is that after he has executed the dependent method of one class, he then proceeds to execute the dependent method of another class.

[krmahadevan]

what version of TestNG are you on @Jinglong233 ?

[Jinglong233]

org.testng testng 7.10.0

[Jinglong233]

@krmahadevan Supplement: The effect I'm aiming for is that after one thread has completed executing a test class, it will then proceed to execute another test class.

[Jinglong233]

@krmahadevan
After my repeated verification, I found that the reason for this phenomenon is that I used the @priority annotation.
Could this be a bug?

[krmahadevan]

No it cannot be a bug. Priority enforces ordering of execution and parallel execution negates that. I dont think these two things should be linked together.

[Jinglong233]

In my XML file, I used "parallel="classes"" and enabled multithreading. Then the expected outcome should be that after one class is executed by a thread, it will proceed to execute another class. Even though I added the Priority annotation, the execution order is still based on the execution sequence of each test case within the current class.
However, the phenomenon I'm observing now is that due to the addition of Priority in my test cases, the thread starts executing another class before completing the execution of the current class.

[krmahadevan]

@Jinglong233 - can you pls create a sample project that can be used to reproduce what you are seeing? I will take a look and get back.

[Jinglong233]

@krmahadevan

@Slf4j
public class Manager {



    public static void initThreadResources() {
        log.info(Thread.currentThread().getName() + " initThreadResources");
    }



    public static void closeThreadResources() {
        log.info(Thread.currentThread().getName() + " closeThreadResources");
    }

}

@Slf4j
public class Base {
    @BeforeSuite
    public void beforeSuite() {
        log.info("beforeSuite");
    }

    @AfterSuite
    public void afterSuite() {
        log.info("afterSuite");
    }

    @BeforeClass
    public void beforeClass() {
        Manager.initThreadResources();
    }

    @AfterClass
    public void afterClass() {
        Manager.closeThreadResources();
    }

}

public class One extends Base {

    @Test
    public void oneDepend() {
        System.out.println("oneDepend  " +  Thread.currentThread().getName());
    }

    @Test(dependsOnMethods = {"oneDepend"})
    public void one() {
        System.out.println("one  " +  Thread.currentThread().getName());
    }
}

public class Three  extends Base {

    @Test
    public void threeDepend() {
        System.out.println("threeDepend  " +  Thread.currentThread().getName());
    }

    @Test(dependsOnMethods = {"threeDepend"})
    public void three() {
        System.out.println("three  " +  Thread.currentThread().getName());
    }
}

public class Two  extends Base {

    @Test
    public void towDepend() {
        System.out.println("towDepend  " +  Thread.currentThread().getName());
    }

    @Test(dependsOnMethods = {"towDepend"})
    public void two() {
        System.out.println("two  " +  Thread.currentThread().getName());
    }
}

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "https://testng.org/testng-1.0.dtd">
    <suite name="Parallel Suite" parallel="classes" thread-count="2">
    <test name="Test Execution">
        <classes>
            <class name="com.jl.zk.zk_JXB.test.One"></class>
            <class name="com.jl.zk.zk_JXB.test.Two"></class>
            <class name="com.jl.zk.zk_JXB.test.Three"></class>
        </classes>

    </test>
</suite>

This is the execution result without any priority.（What I expect）：

[INFO ] 
beforeSuite
[INFO ] 
TestNG-test-Test Execution-2 initThreadResources
[INFO ] 
TestNG-test-Test Execution-1 initThreadResources
oneDepend  TestNG-test-Test Execution-1
towDepend  TestNG-test-Test Execution-2
two  TestNG-test-Test Execution-2
one  TestNG-test-Test Execution-1
[INFO ] 
TestNG-test-Test Execution-2 closeThreadResources
[INFO ] 
TestNG-test-Test Execution-1 closeThreadResources
[INFO ] 
TestNG-test-Test Execution-1 initThreadResources
threeDepend  TestNG-test-Test Execution-1
three  TestNG-test-Test Execution-1
[INFO ] 
TestNG-test-Test Execution-1 closeThreadResources
[INFO ] 
afterSuite

===============================================
Parallel Suite
Total tests run: 6, Passes: 6, Failures: 0, Skips: 0
===============================================

If you add a "priority" attribute to all non-dependent methods, the problem I mentioned earlier will be reproduced.