From 2bbe2eba9358a7a80e245932052eee21e49afb2d Mon Sep 17 00:00:00 2001 From: Fan Lin Date: Fri, 29 Jan 2021 11:23:58 +0800 Subject: [PATCH] be more precise --- docs/en-us/doc/use-mock.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en-us/doc/use-mock.md b/docs/en-us/doc/use-mock.md index c8defc1..0e9fc56 100644 --- a/docs/en-us/doc/use-mock.md +++ b/docs/en-us/doc/use-mock.md @@ -164,4 +164,4 @@ For details, please refer to the [Check Mock Call](en-us/doc/matcher.md) documen > - The name of the test class must be ` + Test` (and in the same package path), which is usually the by-default naming convention of Java project managed by `Maven` or `Gradle`. > - Do NOT access any non-`static` members in mock methods. Currently, methods that is decorated by `@MockMethod` or `@MockContructor` annotations will be automatically modified to `static` methods during runtime. (When mock method contains some statement like _lambda function_, _anonymous class_ or _initiation block_, java compiler will generate additional method during compilation, these mock methods also have to be declared as `static` to avoid non-static dynamical method invoked.) > -> These constraints will be removed in `0.5` versions of `TestableMock`. +> These constraints will change in `0.5` versions of `TestableMock`.