Automation approach for UI which keeps changing
The very first thing that we should check for before starting automation is to verify that Application UI is stable. This is strictly the case when you want to automate the application using UI.
This brings us to two questions
1. Is you application automated using UI only?
2. Is there some form of API/WebServices exposure to your website?
If UI is the only way we can have two approaches
a. Dont try automation at all till UI is stable or atlease 60 – 80 % of the UI is stable. Or the frequency of change is around one every 2 months (Might be little more or less based on your project size)
b. If you any way want to automate and are willing to invest in the automation rework effort that will be required because of constant UI change than I would suggest follow the Page Object model approach. This was you will isolate the UI part in page objects. The most important benifit of this approach is that you will have to make change only in the Page Objects when a UI change occurs.
If you have a webservices or API exposed that are not changing frequently. Forget the UI for the time being just concentrate on the WebService and API testing instead.