2 added 4 characters in body
source | link

Test Executors have nothing to do with how you tell Selenium which objects to use. Personally I do not see any benefit of using PageFactory in the situation like yours. Having stuck to page objects you will have to maintain different sets of objects for each your site which means if the objects set will change you will have to amend allall your Page classes.

I would approach with having regular way of looking up the elements and having the particular paths in properties. When you run that code from wherever you want (e.g. Cucumber CLI - frankly speaking I am not even aware of what it is) you can set the path to your properties for any particular run as environment variable and read that value from your code.

Test Executors have nothing to do with how you tell Selenium which objects to use. Personally I do not see any benefit of using PageFactory in the situation like yours. Having stuck to page objects you will have to maintain different sets of objects for each your site which means if the objects set will change you will have to amend all your Page classes.

I would approach with having regular way of looking up the elements and having the particular paths in properties. When you run that code from wherever you want (e.g. Cucumber CLI - frankly speaking I am not even aware of what it is) you can set the path to your properties for any particular run as environment variable and read that value from your code.

Test Executors have nothing to do with how you tell Selenium which objects to use. Personally I do not see any benefit of using PageFactory in the situation like yours. Having stuck to page objects you will have to maintain different sets of objects for each your site which means if the objects set will change you will have to amend all your Page classes.

I would approach with having regular way of looking up the elements and having the particular paths in properties. When you run that code from wherever you want (e.g. Cucumber CLI - frankly speaking I am not even aware of what it is) you can set the path to your properties for any particular run as environment variable and read that value from your code.

1
source | link

Test Executors have nothing to do with how you tell Selenium which objects to use. Personally I do not see any benefit of using PageFactory in the situation like yours. Having stuck to page objects you will have to maintain different sets of objects for each your site which means if the objects set will change you will have to amend all your Page classes.

I would approach with having regular way of looking up the elements and having the particular paths in properties. When you run that code from wherever you want (e.g. Cucumber CLI - frankly speaking I am not even aware of what it is) you can set the path to your properties for any particular run as environment variable and read that value from your code.