Development

Find any font from any image

Upload an image, and our AI-powered font finder will match it with over 990K+ fonts, including both commercial and free…

Is Content Design Still Relevant?

This isn’t just a minor hiccup; it’s a full-blown crisis. It all becomes too real as everyone scrambles, once again…

In gradle 4.6, how to force all tests in a class gets executed first before moving to tests in next class?

I am using Gradle 4.6 with testng. My test suite has tests organized something like these.

java class1
{
test 1.1
test 1.2
test 1.3
test 1.4
}

java class2
java class3
java class4
java class5

All these classes have total 100 tests in the suite. When I execute the suite, gradle first executes, tests 1.1 and 1.2 and then goes and executes all the tests in class2 to 5 and finally comes back to class 1 to execute 1.3 and 1.4.

Is there a way we can force all the tests in a class to be executed before going to class? For example, it will be helpful, I get all my tests in class1 completes execution, then goes to next class (in any order) and so on.

I do not want to set dependency as any failures will force the dependent test to skip, these are independent tests, eventhough there is some dependency declared tests within the same class.

Jmeter Ramp-up second is dependent on number of request(Sample) and time between sampler inside Thread

For example, there is a thread group named login.

Now this login thread group has 10 request where all requests are parameterized(One API request dependent on other) and time b/w request is 1 secs(Used constant timer)

My question is what is the required ramp up second for thread group?

According to actual calculation read from various sources.If i give thread count 50 and ramp-up seconds as 50 then the time b/w thread is 1 seconds where 50 users will be created in 50 seconds but if i use this scenario how the time b/w request inside the thread will be handled.To run 10 request at least jmeter need 10 seconds since i have used timer

If my scenario is correct then the actual rampup seconds will be dependent on number of request and time b/w request.

Then the Ramp-up-seconds should by calculated as below

Ramp-up-seconds=product of(No of requests,time b/w requests inside thread,No of thread count)

Please make some review on my scenario and provide a answer. If i work with actual Ramp-up-second calculation API paramaratization doesn’t works properly and my jmeter load test script gets failed

Jmeter Test script will be like as below

Make login: Will perform login and extract the authorization token for further requests
create User: Will created user and createduserid will be extracted from response
Fetch User Detail: Will fetch the userdetail for created userid
Logout: Will perform logout

So this should be happen in sequence

and the time b/w request inside thread is 1 seconds used constant timer