-
-
Notifications
You must be signed in to change notification settings - Fork 513
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Skip method parameters in report if description of step provided #469
Comments
@a-en |
@Invictum |
Hello @a-en Unfortunately now such behaving is not implemented, so you should redefine toString method to do what you need. As for me such functionality can be implemented in future, some object can be passed as parameter to Step annotation to make it possible provide custom toString convention rules (as @qualifier for parameterized tests) May be if you can not redefine toString method you can create some wrapper for it, and redefine only toString method - and delegate others? |
Hi Yam! So, I believe there are a couple of possible ways to add more flexibility to @step annotation:
|
@a-en thanks for your ideas!!! |
Hi there!
Due to some specifics, toString() method of the parameter, that I pass to step is huge & non-readable. I thought that the one of the solution would be something like
`
@step("Perform step1")
public void step1(Object someObj) {
step2(object.getName());
}
@step
public void step2(String name) {
//do something with name
}
`
So in the report I expected to see:
I wanted to completely replace the output from step1 in the report by providing explicit description without '{}' and avoid invoke toString() on someObj. This step1() should call step2(), which would produce much prettier output. But now I still get output of someObj's toString(). Is it somehow possible to handle this?
The text was updated successfully, but these errors were encountered: