Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8683679
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 12, 20262026-06-12T22:06:44+00:00 2026-06-12T22:06:44+00:00

I have a problem with JUnit4 and it’s @Test(timeout=xxx) annotation. For example, two tests

  • 0

I have a problem with JUnit4 and it’s @Test(timeout=xxx) annotation. For example, two tests with same body, different name. None of them uses any global variables which can be initialized.
When I run tests it has totally different execution time (First test 0,811s, second 0,143).

It’s very important for me to get similar results. Is there any way to resolve/workaround this problem ?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-12T22:06:45+00:00Added an answer on June 12, 2026 at 10:06 pm

    It is probable that the first test is reported as having taken longer because this includes the setup time JUnit takes to initialize the class. If you have 2 tests that need to run in approximitely the same amount of time, consider adding a third test before the other two just to get the init stuff out of the way.

    Let me know if this works, am curious.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have the same problem as Junit4 and TestNG in one project with Maven
I have a problem with executing tests in JUnit. Imagine you have one test
I have the problem with loading properties from xml inside jUnit test (the same
I have an interesting problem. I am using Ant which executes JUnit tests (test
I have problem SIMILAR to preventing form data reposting, but not quite the same
I have problem developing with live555. I already build the lib-files and example projects
I have an extremely odd problem in my JUnit tests that I just can't
I have a very simple AsyncTask implementation example and am having problem in testing
I have a problem using DatagramSocket. The problem is that I can't run two
I have two different java projects (I'll call them project 1 and Project 2

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.