Google Git
Sign in
chromium / external / github.com / jayway / powermock / refs/tags/powermock-2.0.0-beta.11
tag4f8ae26bd6ccf2c90bcac89d0c2e8b5332dfa9c1
taggerPowerMock Release Tools <powermock.release.tools@outlook.com>Tue May 29 21:06:57 2018
object25f4971fed4f66c4fec6b732fe910ad61ca11c87 
Created new tag powermock-2.0.0-beta.11 by CI build 753

[ci skip-release]
commit25f4971fed4f66c4fec6b732fe910ad61ca11c87[log] [tgz]
authorPowerMock Release Tools <powermock.release.tools@outlook.com>Tue May 29 21:06:57 2018
committerPowerMock Release Tools <powermock.release.tools@outlook.com>Tue May 29 21:06:57 2018
treedb0684acfbf9e9c99bf34307ace8e5ffc6ecffcb
parent03996650b86e0b4fbbbb3168328bee02e3499c17 [diff]
2.0.0-beta.11 release (previous 2.0.0-beta.10) + release notes updated by CI build 753

[ci skip-release]
2 files changed
tree: db0684acfbf9e9c99bf34307ace8e5ffc6ecffcb
  1. .github/
  2. config/
  3. docs/
  4. gradle/
  5. powermock-api/
  6. powermock-classloading/
  7. powermock-core/
  8. powermock-modules/
  9. powermock-reflect/
  10. powermock-release/
  11. tests/
  12. .gitignore
  13. .travis.yml
  14. build.gradle
  15. CONTRIBUTING.md
  16. gradle.properties
  17. gradlew
  18. gradlew.bat
  19. LICENSE.txt
  20. powermock.png
  21. README.md
  22. settings.gradle
  23. version.properties
README.md

PowerMock

Build Status Maven Central Download Javadoc

Usage status: Mockito: Reference Status Easymock: Reference Status jUnit: Reference Status TestNG Reference Status

Writing unit tests can be hard and sometimes good design has to be sacrificed for the sole purpose of testability. Often testability corresponds to good design, but this is not always the case. For example final classes and methods cannot be used, private methods sometimes need to be protected or unnecessarily moved to a collaborator, static methods should be avoided completely and so on simply because of the limitations of existing frameworks.

PowerMock is a framework that extends other mock libraries such as EasyMock with more powerful capabilities. PowerMock uses a custom classloader and bytecode manipulation to enable mocking of static methods, constructors, final classes and methods, private methods, removal of static initializers and more. By using a custom classloader no changes need to be done to the IDE or continuous integration servers which simplifies adoption. Developers familiar with the supported mock frameworks will find PowerMock easy to use, since the entire expectation API is the same, both for static methods and constructors. PowerMock aims to extend the existing API's with a small number of methods and annotations to enable the extra features. Currently PowerMock supports EasyMock and Mockito.

When writing unit tests it is often useful to bypass encapsulation and therefore PowerMock includes several features that simplifies reflection specifically useful for testing. This allows easy access to internal state, but also simplifies partial and private mocking.

Please note that PowerMock is mainly intended for people with expert knowledge in unit testing. Putting it in the hands of junior developers may cause more harm than good.

News

  • 2017-08-12: PowerMock 1.7.1 has been released with one, but significant change: the old API for verifying static mock has been deprecated and a new one has been added. Old API will be removed in version PowerMock 2.0 due to incompatibility with Mockito Public API.
  • 2017-06-16: PowerMock 1.7.0 has been released with support for Mockito 2 (not only beta versions) and new features such as global @PowerMockIgnore as well as bug fixes and other improvements. See release notes and change log for details.
  • 2017-02-03: Johan blogs about how to mock slf4j with PowerMock at his blog

Older News

Documentation

Contributing to PowerMock

Please, read the guideline for a new contributor before start.

Support and discussion

Join the mailing-list here for questions, feedback and support.