
In POM design we will define all elements of a page in one place and there we can also keep all relevant methods along with the definitions of the elements. Test: We will develop a automation script to automate login procedure of ‘facebook’ (i am not going to automate it for real, i am using it as an example)
#APPIUM TUTORIAL AND THINGS TO REMEMBER FULL#
Now i will explain everything based on this structure.At first we will make a test scenario and depending on that we will explain the full model. These are very basic things to maintain.It will keep our project very clean and organized. Define a directory for test reports which will contain our generated test report.Define a directory for test data which will work as our data providers (data required for our test will be here).Define a directory which will contain only spec files of our tests.Define a directory which will contain only page objects files.There is no rule or standards for test automation projects but if we maintain some basic structure it will help a lot for big scale projects.Some basic structures we should consider before starting our project with POM design are stated below If we want we can add more scopes or manipulate configurations according to our requirements.īefore going deep into POM (page object model) design i would like to give an example of a standard test automation project structure according to POM design. I am giving an example with my existing project –įor basic run, these configuration is enough. jasmineNodeOptions (some jasmine configurations can be set here).onComplete, onPrepare, onCleanup different other configuration set for our tests.suite (we can also define test suite here).spec (we will define which spec to run and which not to run over here).framework (By default protractor use jasmine framework, we can define other framework here).capabilities/multicapabilities (means which browser we are going to use for our tests and more scopes of browser will be set here).
#APPIUM TUTORIAL AND THINGS TO REMEMBER HOW TO#
