Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Update Since this is now a year old and I thought about this often, I propose the following:

  • Make junit4 a synonym of junit
  • keep the junit3 Tag

The benefit would be a clearer tag-structure for junit and we will be rid of double tags

Sadly, I can't propose a synonym on SO myself, because thats not allows for version tags.


I hope this is the right place to adress this ;). I saw that this kind of issue was adressed with other tags here before.

I noticed that there are at 3 Junit-tags on stackoverflow, which are both used frequently but without distinction: and / .

Junit4 is the newer Framework for tests, that is based on annotations. But the same kind of questions are also tagged with junit. I think there is no need to keep those tags separated, nowadays most tests are written with the junit 4 Framework (without knowing, that this is the new way).

Junit4-Question with Junit Tag: Cannot capture exception details in @Override in JUnit4, JUnit @Test expected annotation not working

share|improve this question

closed as off-topic by CRABOLO, Infinite Recursion, Emrakul, rene, Doorknob Jan 10 '15 at 13:04

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "This question pertains only to a specific site in the Stack Exchange Network. Questions on Meta Stack Exchange should pertain to our network or software that drives it as a whole, within the guidelines defined in the help center. You should ask this question on the meta site where your concern originated." – CRABOLO, Infinite Recursion, Emrakul, rene, Doorknob
If this question can be reworded to fit the rules in the help center, please edit the question.

+1, Needless to say JUnit 4 is already 5 years old. – GrzegorzOledzki Apr 8 '11 at 18:31
At least "junit3" should stay separate, as it can be used to indicate usage of that (rather old, but still used) version. I see no reason to remove that tag. – Joachim Sauer May 2 '11 at 9:01
some people don't seem to know there is any difference. This question has all 3 Tags:…. I think it is utterly confusing, to have 3 junit Tags, when people seem to confuse what they stand for. – örs May 2 '11 at 10:50

And what when junit5 appears? should be used for general JUnit questions, and or for questions specific only for given version of JUnit. In my opinion such synonimization would be misleading in many cases.

share|improve this answer
Sadly you can't tell people how a tag should be used. They just use it. And as is stated in my question they use it wrong. – örs May 30 '12 at 14:00
You should retag such questions, if you met some. – Danubian Sailor Feb 14 '13 at 6:44

I propose to either:

A) do nothing as I can't decide JUnit should be better off as a synonym for JUnit3 or JUnit4 (newer isn't always right, otherwise Windows 8 would be a synonym for Windows)

B) block JUnit to force people to pick a version (probably the one they are actually using)

share|improve this answer
b) won't work. You'd have to retag every single junit question to junit3 or junit4 before that! And junit3 is so old, most people will only use junit4 now and maybe won't even know about version numbers. This tag should be transparent for users and not more complicated :D – örs Mar 16 '12 at 13:08

Not the answer you're looking for? Browse other questions tagged .