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 6617431
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 25, 20262026-05-25T20:42:13+00:00 2026-05-25T20:42:13+00:00

Maven 3.x.x complains about my mock TestPacket class that I use for another real

  • 0

Maven 3.x.x complains about my mock “TestPacket” class that I use for another real test:

java.lang.Exception: No runnable methods

How can I avoid Maven complaining about this?
I did this for now (in TestPacket):

@Test
public void workaround() {
}

But there should be another clean way…

Thank you for your time!

Andrew

  • 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-05-25T20:42:14+00:00Added an answer on May 25, 2026 at 8:42 pm

    This is more of an JUnit issue than a maven one. If you don’t want your TestPacket class to be treated as a JUnit test class by JUnit, annotate it (at the class level) with JUnit’s @Ignore annotation

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

Sidebar

Related Questions

I have a multi-module Maven project that makes use of WAR overlays (stack of
I have two Eclipse Maven Java projects. A domain project that is laden with
I have a maven POM that I'd like to use as a template, producing
Maven 2 does not seem to consider my @Test and @Ignore annotations. How do
What Maven repository can I use for EJB 3.1 API dependency?
So maven downloads the pom then declares that it is missing. Then it proceeds
My following script is producing an error (it complains about expecting 'then' keyword before
I have a class that must be initialized with an absolute pathname. The thing
Maven had a long history and is well supported in the Java world. NMaven
My maven reports are working great, all except Checkstyle and test xref. My test

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.