Build Effective Automation with

1. Build Effective Automation with Q&A Automation Solutions

2. What is Oculus? • Oculus – is a set of implemented solutions and techniques for development, analysis and management which are used to provide the reliable QA Automation process and build robust, scalable and flexible automation frameworks for your applications.

3. Basic solutions • Reporting System • Projects Management System • Test Management System • Project Documentation Library • Test Run Management System • Test Run Framework • WEB Automation Extensions • Oculus Selenium Framework • Oculus HTTP Sniffer (Capturing HTTP requests)

4. Oculus Architecture User DB Oculus Main Server Test Run Manager Server Test Run Manager Agent (1) Test Run Manager Agent (n) ... Automation Project & TRF Automation Project & TRF

5. Automation Processes with Oculus On the following diagram you can see major processes which may occur in automation projects. Oculus has an implementation for each of them.

6. Project Management • Each automation project contains subprojects (may be treated as flows or business components of the application which is being tested within the project) • Dashboard – displays the charts of test runs within the project. Could be used for tracking the project quality • Build Management – manages the automation project versioning

7. Documentation management • Documentation is presented in a tree structure – You are able to create folders of any hierarchy within the project documentation library • Test-Cases– allows to create simple test-cases with BBCode decoration • Files – uploading files to project library

8. Test Development The test development within Oculus system was designed in Oculus Test Run Framework (TRF). TRF is a Java library which is used for running automation tests. The test in TRF is presented as Java class with a set of consequent actions with different features.

9. Test Run Framework features • Running with Test Dependencies – test may depend on the parameters of other tests • Rollback – test can be designed with rollback methods which will be used to cancel all the changes made by the test. This is useful when you need to run the tests for monitoring the production environment • Test Injection – allows to inject other tests in the current test. This is useful when you need to run a set of tests as a single test or just to reduce coupling in your code. • Errors handling – using methods for handling the actions which were interrupted with some error • Hierarchical Report – the report was designed as a tree structure. This allows you to separate the report content to logical components • Event Listeners – allows using methods-subscribers for some global events. Could be used for AOP implementation (Aspect-Oriented-Programming) for tests which use Test Injection

10. Test Management • Test Customization – allows to setup input and output parameters for the test. These parameters will be used in Test Run Management System • Link with Test-Case from Project Documentation Library. When the test is linked with some test-case, the test-case content will be displayed on a test page

11. Test Running with Oculus Test Run Manager (TRM) • Managing Tasks • Task is designed as a set of suites with tests • Each suite contains tests with dependencies and customized parameters • Launching against the selected agent (machine which is connected to the TRM and used for running test) • Customizing the suite parameters – allows to choose the suite parameters before the task launching • Scheduling Tasks – using the time scheduler to run the tasks at needed time point • Active Tasks Monitoring – the page with active tasks of the current user. Allows to monitor the tasks running (percent of completed tests, task status, suite statuses etc.)

12. Automation Tricks with TRM • Building your own test scenario based on prepared test bricks. The tests could be separated to logical components and then gathered in one suite and linked together with test dependencies. This will allow to build your own test logic just from Test Run Manager.For instance you can create simple tests for such actions as: create user, login, logout and etc. Splitting website model to business components will allow you to reduce coupling in the code and organize flexible and scalable test running.

13. Reports Analyzing with Oculus Reporting System • Filtering Reports – allows to filter reports by different parameters (status, suite, project, etc.) • Managing Filters – you can save the report filter and use it further • View Report – the reports have informative design and are displayed in a tree structure with useful browsing features

14. Report Design • Hierarchical Content– All the report content is structured in hierarchical view which allows to combine report parts into logical components • Big amount of logo icons – Each report node can be marked with the icon from the standard icon-set of oculus which allows to understand the report without entering its details • BBCode in report text – You can design your reports as you wish using the BBCode tags of the Oculus Reporter

15. Report Example

16. Oculus Selenium Framework • Building website model – In OSF there is a set of components (Browser, Page, Frame, web elements and etc.) which could be used to build full website model and separate element definitions from tests. You first develop the Page Model of the website which is being tested and then build your tests based on this model. If there are changes on the website (changes in design) you change only the model but not all the tests • Decreasing the elements dependency with Form Generators – There is a trick which allows you to inject your own built html forms into the page of the website during the test running. This allows you to decrease the test dependencies on the element definitions and build the reliable end-point testing. For instance you can inject the form for sign-in and use it in all tests which need it and if the design of sign-in page on the website is changed your tests will work without any problems • Automatic creation of screenshots – If something goes wrong on the website and you click on elements which do not exist OSF will automatically create a screenshot of the page and upload it to the Oculus Main Server. • Attached Behavior - During automation test development you can face the problem of providing tests which will work in all browsers. This happens because sometimes different website elements could be handled in a different way for each browser. And this becomes a serious problem for the automation. Oculus Selenium Framework gives you an opportunity to abstract the behavior for any web element from the test.