blocks|key|4409475|text|获得测试方法名称的更简单方法是使用@BeforeMethod并注入Method。请参阅TestNG的文档here。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4409476|只需将名称存储在某个位置并在日志中使用它(为什么不在@AfterMethod中使用它?)|4409477|entityMap|0|LINK|mutability|MUTABLE|url|https://testng.org/doc/documentation-main.html#native-dependency-injection^0|H|D|X|6|1G|4|0|0|Q|C|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@$9|U|A|V|1|W]]|E|$]]|$1|F|3|G|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

The simpler way to have a test method name is by using a <code>@BeforeMethod</code> and injecting the <code>Method</code>. See TestNG's documentation, <a href="https://testng.org/doc/documentation-main.html#native-dependency-injection" rel="nofollow noreferrer">here</a>.
Just store the name somewhere and use it in your log (why not in a <code>@AfterMethod</code> ?)

blocks|key|4409498|text|通过向下搜索堆栈跟踪来执行Log4J+finds+the+method+name，直到找到必须传入的目标类名，然后读取方法名。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4409499|在您的代码中，您可以使用类似的技术-代替静态方法Utils，您可以在测试中创建一个实例，传入测试的类：|4409500|Utils+utils+=+new+Utils(MyTest.class);|code-block|syntax|javascript|4409501|然后在Utils.logTitle()方法中使用前面提到的搜索技术。|style|CODE|4409502|Utils.logTitle()将向前搜索新创建的Throwable的堆栈跟踪元素，直到找到具有所需目标类的第一个元素。|4409503|entityMap|0|LINK|mutability|MUTABLE|url|http://grepcode.com/file/repo1.maven.org/maven2/log4j/log4j/1.2.17/org/apache/log4j/spi/LocationInfo.java?av=f#134^0|D|R|0|0|0|0|3|G|0|0|G|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|13|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|14|8|@$A|15|B|16|M|N]]|9|@]|C|$]]|$1|O|3|P|5|6|7|17|8|@$A|18|B|19|M|N]]|9|@]|C|$]]|$1|Q|3|-4|5|6|7|1A|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]]]

<a href="http://grepcode.com/file/repo1.maven.org/maven2/log4j/log4j/1.2.17/org/apache/log4j/spi/LocationInfo.java?av=f#134" rel="nofollow">Log4J finds the method name</a> by searching down the stack trace until it finds the target class name which must be passed in, then reads the method name.

In your code, you could use a similar technique - instead of a static method Utils you could create an instance in your test, passing in the class of the test:

<pre><code>Utils utils = new Utils(MyTest.class);
</code></pre>

Then use the previously mentioned search technique in the <code>Utils.logTitle()</code> method.

<code>Utils.logTitle()</code> would search forwards through stack trace elements of a newly created Throwable until it finds the first element with the desired target class.

blocks|key|4409520|text|我认为是特定的深度导致了问题，在您的场景中是2。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4409521|所以，与其写|4409522|String+method+=+Thread.currentThread().getStackTrace()[2].getMethodName();|code-block|syntax|javascript|4409523|如果你写|4409524|StackTraceElement[]+ste+=+Thread.currentThread().getStackTrace();
String+method+=+null;
boolean+doNext+=+false;
for+(StackTraceElement+s+:+ste)+{
+++++++if+(doNext)+{
++++++++++method+=+s.getMethodName();
++++++++++return;
+++++++}
+++++++doNext+=+s.getMethodName().equals("getStackTrace");
+++}|4409525|它只适用于JDK+1.5%2B。|4409526|另一个选项如下：|4409527|String+method+=+new+Object(){}.getClass().getEnclosingMethod().getName();|4409528|或者更慢的选项是：|4409529|String+method+=+new+Exception().getStackTrace()[0].getMethodName();|4409530|因为这样每次都会创建一个异常的实例。|4409531|希望这能帮到你。|4409532|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|14|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|15|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|16|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|17|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|18|8|@]|9|@]|A|$]]|$1|Q|3|R|5|F|7|19|8|@]|9|@]|A|$G|H]]|$1|S|3|T|5|6|7|1A|8|@]|9|@]|A|$]]|$1|U|3|V|5|F|7|1B|8|@]|9|@]|A|$G|H]]|$1|W|3|X|5|6|7|1C|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1D|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|11|$]]

I think its the specific depth that is causing the issue which is 2 in your scenario. 

So, instead of writing 

<pre><code>String method = Thread.currentThread().getStackTrace()[2].getMethodName();
</code></pre>

if you write

<pre><code>StackTraceElement[] ste = Thread.currentThread().getStackTrace();
String method = null;
boolean doNext = false;
for (StackTraceElement s : ste) {
 if (doNext) {
 method = s.getMethodName();
 return;
 }
 doNext = s.getMethodName().equals("getStackTrace");
 }
</code></pre>

It will work only for JDK 1.5+

The other option is as below:

<pre><code>String method = new Object(){}.getClass().getEnclosingMethod().getName();
</code></pre>

Or a slower option will be :

<pre><code>String method = new Exception().getStackTrace()[0].getMethodName();
</code></pre>

As this will create an instance of Exception everytime.

Hope that helps you out.

blocks|key|4409349|text|Log4j+2使用记录器的全限定类名来定位从中调用记录器的类和方法。查找该位置的代码如下所示。请随意使用它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4409350|请注意，循环从堆栈跟踪的底部开始；这对于检测以递归方式调用记录器的异常情况(可能是从记录的对象的toString()方法)是必要的。在这种情况下，我们希望报告调用Logger的第一个类/方法，而不是最后一个，因此我们别无选择，只能自下而上遍历堆栈跟踪。|offset|length|style|CODE|4409351|public+static+StackTraceElement+calcLocation(final+String+fqcnOfLogger)+{
++++if+(fqcnOfLogger+==+null)+{
++++++++return+null;
++++}
++++//+LOG4J2-1029+new+Throwable().getStackTrace+is+faster+
++++//+than+Thread.currentThread().getStackTrace().
++++final+StackTraceElement[]+stackTrace+=+new+Throwable().getStackTrace();
++++StackTraceElement+last+=+null;
++++for+(int+i+=+stackTrace.length+-+1;+i+>+0;+i--)+{
++++++++final+String+className+=+stackTrace[i].getClassName();
++++++++if+(fqcnOfLogger.equals(className))+{
++++++++++++return+last;
++++++++}
++++++++last+=+stackTrace[i];
++++}
++++return+null;
}|code-block|syntax|javascript|4409352|entityMap^0|0|1C|A|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|S|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Log4j 2 uses the fully qualified class name of the Logger to locate the class and method from which the Logger was called. The code to find the location follows below. Feel free to use it. 

Note that the loop starts from the bottom of the stacktrace; this is necessary to detect exceptional cases where the logger is called recursively (perhaps from the <code>toString()</code> method of an object that was logged). In such cases we want to report the first class/method that called the Logger, not the last one, so we have no choice but to walk the stack trace from the bottom up.

<pre><code>public static StackTraceElement calcLocation(final String fqcnOfLogger) {
 if (fqcnOfLogger == null) {
 return null;
 }
 // LOG4J2-1029 new Throwable().getStackTrace is faster 
 // than Thread.currentThread().getStackTrace().
 final StackTraceElement[] stackTrace = new Throwable().getStackTrace();
 StackTraceElement last = null;
 for (int i = stackTrace.length - 1; i &gt; 0; i--) {
 final String className = stackTrace[i].getClassName();
 if (fqcnOfLogger.equals(className)) {
 return last;
 }
 last = stackTrace[i];
 }
 return null;
}
</code></pre>

For logging purposes, I created a method logTitle() that prints out the calling method name for our TestNG tests. Sample code is below.

<pre><code>@Test
public void test1() throws Exception {
 method1();
}

public static void method1() throws Exception {
 Utils.logTitle(2);
}
</code></pre>

...

<pre><code>public static void logTitle(Integer level) throws Exception {

 // Gets calling method name
 String method = Thread.currentThread().getStackTrace()[2].getMethodName();
 // This would get current method name
 switch (level) {
 case 1:
 logger.info("=======================================================");
 logger.info(method);
 logger.info("=======================================================");
 break;
 case 2:
 logger.info("------------------------------------");
 logger.info(method);
 logger.info("------------------------------------");
 break;
 case 3:
 logger.info("---------------------");
 logger.info(method);
 logger.info("---------------------");
 break;
 case 4:
 logger.info("--------- " + method + " ------------");
 break;
 default:
 logger.info(method);
 }
}
</code></pre>

The problem is I am getting different results for logTitle() on two different machines.

Everyone's laptop returns correctly:

<pre><code>2016-06-20 14:22:06 INFO - ------------------------------------
2016-06-20 14:22:06 INFO - method1
2016-06-20 14:22:06 INFO - ------------------------------------
</code></pre>

Our dev unix box returns differently:

<pre><code>2016-06-20 14:42:26 INFO - ------------------------------------
2016-06-20 14:42:26 INFO - logTitle
2016-06-20 14:42:26 INFO - ------------------------------------
</code></pre>

This works correctly on everyone else's laptop, just not the dev unix box. I think the dev unix box is using IBM's version of Java, while everyone else is using Oracle's version of Java, but not sure if that is the culprit or not.

Any ideas?

Getting different results for getStackTrace()[2].getMethodName()

Java

出于日志记录的目的，我创建了一个logTitle()方法，它为我们的TestNG测试打印出调用方法的名称。示例代码如下。@Testpublic void test1() throws Exception {    method1();}public static void method1() throws Except...

问获取getStackTrace()[2].getMethodName()的不同结果
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问获取getStackTrace()[2].getMethodName()的不同结果EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问获取getStackTrace()[2].getMethodName()的不同结果
EN