For multiple products (with different teams) creating one huge solution,<\/p>\n

How would you structure the automation framework? Here are few options:<\/p>\n

Solution 1 – Separate frameworks for all products<\/p>\n

Solution 2 \u2013 One framework for all products across the same automation type<\/p>\n

Solution 3 \u2013 Common framework and libraries for each automation type, with separate POM and tests layer for each product<\/p>\n

There can be other ways, these are the three I have seen been used over the years.<\/p>\n

Which one do you think would suit best for this structure:<\/p>\n

– Different teams working on separate products eventually all joining to become one huge solution
\n– All these products have separate time-lines, but are also interdependent on one another
\n– End to End tests will obviously be needed to verify across all the product lines as one holistic solution<\/p>\n

(I don\u2019t want to share my choice upfront to avoid any bias)<\/p>\n<\/div><\/span>