Open Husterknupp opened 10 years ago
When thinking about it I guess that it would be possible to merge them to one method:
assertWorkingInputVerificationOfFeatureDefinitionDialogOpenedBy(AbstractButton button)
assertWorkingInputVerificationOfFeatureDefinitionDialogOpenedWith(AbstractButton button)
assertWorkingInputVerificationOfFeatureDefinitionDialogByClicking(AbstractButton button)
...
What I like about this solution:
What I don't like / what we need to be aware of:
clickEditButtonAndCheckComponentVerification()
has some different logic; we therefore need either an if statement in the merged method or just set the input values in the add feature dialog as well (does not hurt anyone)Why is this tagged as backend? I'd rather say that input verification is a front-end issue.
Why is this tagges as duplicate? If an issue is duplicate, please clearly state which issue it is duplicating in the description.
Oh sorry for that. I misunderstood the meaning of the duplicate tag.
Yeah you cannot delete issues. So if you create one that will not be done, set it on "won't fix" and if you create one duplicate by mistake, set it "duplicate".
The
SwingMenuTestUtil
has two methods doing pretty similar things while the pointing out the difference between them is quite hard. They have to be reworked or at least should the names be improved, in order to make the difference between them more obvious.clickAddButtonAndCheckComponentVerification()
clickEditButtonAndCheckComponentVerification()
Same applies for:
openAndCancelEditFeatureDialog
openAndCancelAddFeatureDialog