Warm tip: This article is reproduced from stackoverflow.com, please click
java testng appium assert assertion

Can you make assertTrue error messages more specific?

发布于 2020-03-27 15:43:37

I use testNG's assertTrue quite a lot to verify for example if transactions are correct

public void verifyAmount(WebElement element, String someText){
assertTrue(element.getText().contains(someText));
}

and when it fails it says 

java.lang.AssertionError: did not expect to find [true] but found[false]

Is it possible to change assertion error to say what exactly went wrong, not just true/false statement? Is it possible to make that message more specific? Is there a way to make assertion error say :

java.lang.AssertionError: did not expect to find [10.000 $] but found[3000 $]
Questioner
Vedran Zenzerović
Viewed
27
分享
Stultuske 2020-01-31 17:17

You could turn this:

public void verifyAmount(WebElement element, String someText){
assertTrue(element.getText().contains(someText));
}

into:

public void verifyAmount(WebElement element, String someText, String message){
assertTrue(element.getText().contains(someText), message);
}

and pass the error message you feel should be given there.

EDIT: I'm used to using other assert methods, which take the message as first param, but Long Nguyen is right in his answer: TestNG accepts the message as last parameter of the assertTrue.

Vedran Zenzerović 2020-01-31 17:36:00

yes was confused about that but managed it to work

Related issues

1
Alternative approach for checking data types to build an object
2
Is it possible to get first and last name from Google Authentication on Firebase?
3
Constructor that receives TXT files to read and store them
4
Logback with Elastic Beanstalk
5
Camel Predicate Example in xml DSL
6
How do I get user input validation into my java calculator program?
7
firebase getting exact childs from database
8
Listener for custom dialog null
9
JFrame very small
10
AWS Elastic Beanstalk Application Logging with Logback