mockit.Delegate Maven / Gradle / Ivy
/*
* JMockit Expectations
* Copyright (c) 2006-2010 Rogério Liesenfeld
* All rights reserved.
*
* Permission is hereby granted, free of charge, to any person obtaining
* a copy of this software and associated documentation files (the
* "Software"), to deal in the Software without restriction, including
* without limitation the rights to use, copy, modify, merge, publish,
* distribute, sublicense, and/or sell copies of the Software, and to
* permit persons to whom the Software is furnished to do so, subject to
* the following conditions:
*
* The above copyright notice and this permission notice shall be
* included in all copies or substantial portions of the Software.
*
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
* EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
* MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
* IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
* CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
* TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
* SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
*/
package mockit;
/**
* An empty interface to be used with the {@link Expectations#result} field, in order to allow test
* code to define invocation results (return values or thrown errors/exceptions) based on
* test-specific logic.
*
* An implementation of this interface should define a method matching the signature of the recorded
* method/constructor call.
* That is, they should have the same name and parameters. In the case of delegating a constructor,
* a delegate method should still be used, with name "$init".
*
* Alternatively, for the common case where the delegate implementation class defines a
* single method, the name is allowed to be different from the recorded method.
* The parameters should still match, though. Besides giving more flexibility, this ability also
* prevents the test from breaking in case the recorded method is renamed.
* Note that if the delegate class defines two or more methods ({@code private} ones included, if
* any), then exactly one of them must match both the name and the parameters of the
* recorded method.
*
* At replay time, when that method/constructor is called the corresponding "delegate" method will
* be called to produce the desired result. The arguments passed to the delegate method will be the
* same as those received by the recorded invocation during replay. The result can be any return
* value compatible with the recorded method's return type, or a thrown error/exception.
*
* Even {@code static} methods in the mocked type can have delegates, which in turn can be static or
* not. The same is true for {@code private}, {@code final}, and {@code native} methods.
*
* In the Tutorial
*
* Sample tests:
* DocumentManager_JMockit_Test
*/
public interface Delegate
{
}
© 2015 - 2025 Weber Informatics LLC | Privacy Policy