Open S4064172 opened 2 years ago
We added the basic flow to manage the clusterin of the method that has the same name. Now we have to tune the flow under more complex test and manage the common parameters
Moreover, we have to add some constraints in oreder to create the correct cluster (ie: the cluster should be created only if there is a sendKey command or some parameter)
We changed the flow in order to manage the commons parameters:
We notice that the tool is not able to understand if the method is already created when the args have a different name
we fixed the problem related to the functions with the same body but different parameters
but it is always sensible to the order. I mean that if the two methods have the same command with a different order, for the tool the methods are different.
Moreover, the clustering doesn't work if the method as the selenium commands .... in this case we got an exception
we fixed the problem related to the locator and we also added a flow to force the creation of a function for each locator
we notice that if the tester misses some assessor command the tool is not always able to fill it correctly and so sometimes the tool can use different PO declaration
With this feature, we want to aggregate the methods that have the same name even if they have different parameters. The classic example is the form where the tester can fill all or some fields.