Home
IDEs Support (IntelliJ Platform) | JetBrains
Contact Support
Community
Sign in

Rliesenfeld

Avatar
  • Total activity 4
  • Last activity January 30, 2018 12:47
  • Member since January 28, 2018 16:59
  • Following 0 users
  • Followed by 0 users
  • Votes 0
  • Subscriptions 1
Activity overview Posts (0) Comments (3)
  • Rliesenfeld commented, January 30, 2018 12:47
    I tried running all tests under the "mockit" package.
    1. Community
    2. IntelliJ IDEA Users
    3. "0 test classes found in package" after upgrading to 2017.3
    • 0 votes
  • Rliesenfeld commented, January 28, 2018 17:00
    BTW, adding "-Djunit4.search.4.tests.in.classpath=false" makes no difference.   However, what *does* avoid the problem is to comment out the "junit-jupiter-engine" dependency in the "main" module's...
    1. Community
    2. IntelliJ IDEA Users
    3. "0 test classes found in package" after upgrading to 2017.3
    • 0 votes
  • Rliesenfeld commented, January 28, 2018 16:59
    Hello Anna,   I am using latest IntelliJ (2017.3.3, community edition), and I am seeing this problem in my old OSS project (https://github.com/jmockit/jmockit1) which is all properly configured, an...
    1. Community
    2. IntelliJ IDEA Users
    3. "0 test classes found in package" after upgrading to 2017.3
    • 0 votes
Copyright © 2000– JetBrains s.r.o.