-
-
Notifications
You must be signed in to change notification settings - Fork 760
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
Addition to the #579 #585
Addition to the #579 #585
Conversation
The chaining of the activity parameter setting.
@email2vimalraj You could review it too. |
driver.startActivity(activity); | ||
return true; | ||
}).test(driver)); | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
extra line here
Nice Idea @TikhomirovSergey |
activity.setIntentFlags("0x4000000"); | ||
activity.setOptionalIntentArguments("-d \"TestIntent\" -t \"text/plain\""); | ||
driver.startActivity(activity); | ||
return true; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is the whole construction with assertTrue and return true really necessary?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mykola-mokhnach
Yes. It is for codecy checkings. It requires assertions. Also I have an opinion that assertions inside tests methods is the good style.
@SrinivasanTarget @mykola-mokhnach I will fix the issue later. |
@TikhomirovSergey : Good idea. Kindly update the |
Change list
The chaining of the activity parameter setting.
Types of changes
What types of changes are you proposing/introducing to Java client?